| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in libxml2 2.9.0 and classified as critical. Affected is the function xmldecl_done of the file parser.c. The manipulation leads to memory corruption.
This vulnerability is traded as CVE-2013-1970. There is no exploit available.
Details
A vulnerability was found in libxml2 2.9.0 (Document Processing Software) and classified as very critical. This issue affects the function xmldecl_done of the file parser.c. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2013-1969. Reason: This candidate is a duplicate of CVE-2013-1969. Notes: All CVE users should reference CVE-2013-1969 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage.
The weakness was shared 12/14/2012 by Zan Dobersek as 690202 as not defined bug report (Website). The advisory is shared at bugzilla.gnome.org. The public release happened without involvement of the project team. The identification of this vulnerability is CVE-2013-1970 since 02/19/2013. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/03/2013).
Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.gnome.org. A possible mitigation has been published 3 months after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at OSVDB (92252†) and Secunia (SA53061†). The entry VDB-8248 is related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 10.0VulDB Meta Temp Score: 9.5
VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| 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: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Patch: git.gnome.org
Timeline
12/14/2012 🔍02/12/2013 🔍
02/19/2013 🔍
04/16/2013 🔍
04/25/2013 🔍
10/03/2013 🔍
Sources
Advisory: 690202Researcher: Zan Dobersek
Status: Not defined
CVE: CVE-2013-1970 (🔍)
GCVE (CVE): GCVE-0-2013-1970
GCVE (VulDB): GCVE-100-8249
Secunia: 53061 - libxml2 Multiple Use-After-Free Vulnerabilities, Highly Critical
OSVDB: 92252 - Libxml2 parser.c xmldecl_done Function Buffer Reallocation Missing Pointer Update Buffer Overflow
See also: 🔍
Entry
Created: 04/16/2013 17:59Updated: 10/03/2013 12:15
Changes: 04/16/2013 17:59 (48), 10/03/2013 12:15 (8)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.