Mini-XML 3.2 memory leak ⚔ [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.5	$0-$5k	0.00

Summaryinfo

A vulnerability, which was classified as problematic, was found in Mini-XML 3.2. Affected by this issue is some unknown functionality. Such manipulation leads to memory leak. This vulnerability is uniquely identified as CVE-2021-42859. No exploit exists. The existence of this vulnerability is still disputed at present.

Detailsinfo

A vulnerability was found in Mini-XML 3.2. It has been rated as problematic. Affected by this issue is some unknown functionality. The manipulation with an unknown input leads to a memory leak vulnerability. Using CWE to declare the problem leads to CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. Impacted is availability.

The weakness was disclosed 05/26/2022 as 286. The advisory is available at github.com. This vulnerability is handled as CVE-2021-42859 since 10/25/2021. The technical details are unknown and an exploit is not 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.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

Mini-XML

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

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

VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

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: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory leak
CWE: CWE-401 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

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

10/25/2021 🔍
05/26/2022 +213 days 🔍
05/26/2022 +0 days 🔍
08/04/2024 +801 days 🔍

Sourcesinfo

Advisory: 286
Status: Confirmed
Disputed: 🔍

CVE: CVE-2021-42859 (🔍)
GCVE (CVE): GCVE-0-2021-42859
GCVE (VulDB): GCVE-100-200762

Entryinfo

Created: 05/26/2022 17:32
Updated: 08/04/2024 09:25
Changes: 05/26/2022 17:32 (36), 05/30/2022 14:57 (1), 08/04/2024 09:25 (35)
Complete: 🔍
Cache ID: 216::103