libxml2 parser.c xmlParseAttValueComplex Long String memory corruption

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.
9.5$0-$5k0.00

Summaryinfo

A vulnerability was found in libxml2 and classified as problematic. This vulnerability affects the function xmlParseAttValueComplex of the file parser.c. The manipulation as part of Long String results in memory corruption. This vulnerability is reported as CVE-2012-5134. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in libxml2 (Document Processing Software) (the affected version is unknown). Affected is the function xmlParseAttValueComplex of the file parser.c. The manipulation as part of a Long String leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

Heap-based buffer underflow in the xmlParseAttValueComplex function in parser.c in libxml2 2.9.0 and earlier, as used in Google Chrome before 23.0.1271.91 and other products, allows remote attackers to cause a denial of service or possibly execute arbitrary code via crafted entities in an XML document.

The weakness was disclosed 11/26/2012 by Jüri Aedla (Inferno) with Google Chrome Security Team as confirmed advisory (Website). The advisory is shared for download at googlechromereleases.blogspot.dk. This vulnerability is traded as CVE-2012-5134 since 09/24/2012. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available. This issue was originally reported in Google Chrome, where it was fixed in version 23.0.1271.91.

The vulnerability scanner Nessus provides a plugin with the ID 74846 (openSUSE Security Update : libxml2 (openSUSE-SU-2012:1647-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 216049 (VMWare ESXi 5.1.0 Patch Complete Update 1 Missing (KB2041632)).

Upgrading eliminates this vulnerability. A possible mitigation has been published 2 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (80294), Tenable (74846), SecurityFocus (BID 56684†), OSVDB (87882†) and Secunia (SA48000†). Further details are available at code.google.com. The entries VDB-4661, VDB-4619, VDB-4675 and VDB-4996 are pretty similar. VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Name

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 9.5

VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
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

Nessus ID: 74846
Nessus Name: openSUSE Security Update : libxml2 (openSUSE-SU-2012:1647-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 850379
OpenVAS Name: SuSE Update for Chromium openSUSE-SU-2012:1637-1 (Chromium)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

02/22/2012 🔍
09/24/2012 +215 days 🔍
11/26/2012 +63 days 🔍
11/26/2012 +0 days 🔍
11/27/2012 +1 days 🔍
11/27/2012 +0 days 🔍
11/27/2012 +0 days 🔍
11/30/2012 +3 days 🔍
12/07/2012 +7 days 🔍
06/13/2014 +553 days 🔍
04/28/2019 +1780 days 🔍

Sourcesinfo

Advisory: googlechromereleases.blogspot.dk
Researcher: Jüri Aedla (Inferno)
Organization: Google Chrome Security Team
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2012-5134 (🔍)
GCVE (CVE): GCVE-0-2012-5134
GCVE (VulDB): GCVE-100-7032

OVAL: 🔍

X-Force: 80294
SecurityFocus: 56684 - Google Chrome Prior to 23.0.1271.91 Multiple Security Vulnerabilities
Secunia: 48000 - libxml2 Denial of Service and Buffer Underflow Vulnerabilities, Highly Critical
OSVDB: 87882
SecurityTracker: 1027815

Misc.: 🔍
See also: 🔍

Entryinfo

Created: 11/30/2012 08:38
Updated: 04/28/2019 18:10
Changes: 11/30/2012 08:38 (84), 04/28/2019 18:10 (6)
Complete: 🔍
Cache ID: 216:B56:103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!