answer up to 1.0.5 Business Logic logic error

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.8$0-$5k0.00

Summaryinfo

A vulnerability was found in answer up to 1.0.5. It has been rated as problematic. The impacted element is an unknown function of the component Business Logic Handler. Performing a manipulation results in logic error. This vulnerability is identified as CVE-2023-1541. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as problematic has been found in answer up to 1.0.5. This affects an unknown function of the component Business Logic Handler. The manipulation with an unknown input leads to a logic error vulnerability. CWE is classifying the issue as CWE-840. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Business Logic Errors in GitHub repository answerdev/answer prior to 1.0.6.

The weakness was released 03/21/2023. The advisory is shared at huntr.dev. This vulnerability is uniquely identified as CVE-2023-1541 since 03/21/2023. Neither technical details nor an exploit are publicly available.

Upgrading to version 1.0.6 eliminates this vulnerability. Applying the patch 15390adbfcd5fd37af4661f992f8873ae5a6b840 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-1021). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.8
VulDB Meta Temp Score: 4.8

VulDB Base Score: 4.7
VulDB Temp Score: 4.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 3.8
NVD Vector: 🔍

CNA Base Score: 6.0
CNA Vector (huntr.dev): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Logic error
CWE: CWE-840
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: answer 1.0.6
Patch: 15390adbfcd5fd37af4661f992f8873ae5a6b840

Timelineinfo

03/21/2023 🔍
03/21/2023 +0 days 🔍
03/21/2023 +0 days 🔍
07/06/2025 +838 days 🔍

Sourcesinfo

Advisory: 15390adbfcd5fd37af4661f992f8873ae5a6b840
Status: Confirmed

CVE: CVE-2023-1541 (🔍)
GCVE (CVE): GCVE-0-2023-1541
GCVE (VulDB): GCVE-100-223461
EUVD: 🔍

Entryinfo

Created: 03/21/2023 09:37
Updated: 07/06/2025 16:57
Changes: 03/21/2023 09:37 (50), 04/12/2023 09:26 (1), 04/12/2023 09:28 (11), 07/06/2025 16:57 (15)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!