Precomp 0.4.8 std::bad_alloc privilege escalation ⚔ [Disputed]

HistoryDiffrelatejsonxmlCTI

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.
5.3	$0-$5k	0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Precomp 0.4.8. Affected by this issue is the function std::bad_alloc. Performing a manipulation results in an unknown weakness. This vulnerability is known as CVE-2023-31854. No exploit is available. The actual existence of this vulnerability is currently in question.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Precomp 0.4.8. The impact remains unknown. The summary by CVE is:

std::bad_alloc is mishandled in Precomp 0.4.8. NOTE: this is disputed because it should be categorized as a usability problem.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-31854 since 04/29/2023. Technical details are known, but no exploit is available.

The real existence of this vulnerability is still doubted at the moment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

Precomp

Version

0.4.8

CPE 2.3info

🔍

CPE 2.2info

🔍

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

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

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

04/29/2023 🔍
03/27/2024 +333 days 🔍
03/27/2024 +0 days 🔍
08/02/2024 +128 days 🔍

Sourcesinfo

Advisory: 139
Status: Not defined
Disputed: 🔍

CVE: CVE-2023-31854 (🔍)
GCVE (CVE): GCVE-0-2023-31854
GCVE (VulDB): GCVE-100-258105

Entryinfo

Created: 03/27/2024 07:01
Updated: 08/02/2024 18:37
Changes: 03/27/2024 07:01 (50), 05/05/2024 14:29 (1), 08/02/2024 18:37 (1)
Complete: 🔍
Cache ID: 216::103