libxml2 up to 2.9.3 parser.c xmlParseElementDecl memory corruption
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
8.5 | $0-$5k | 0.00 |
A vulnerability was found in libxml2 up to 2.9.3 (Document Processing Software). It has been rated as very critical. This issue affects the function xmlParseElementDecl
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:
The xmlParseElementDecl function in parser.c in libxml2 before 2.9.4 allows context-dependent attackers to cause a denial of service (heap-based buffer underread and application crash) via a crafted file, involving xmlParseName.
The weakness was released 06/09/2016 (Website). The advisory is shared at debian.org. The identification of this vulnerability is CVE-2016-4447 since 05/02/2016. The exploitation is known to be easy. 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 08/23/2022).
The vulnerability scanner Nessus provides a plugin with the ID 91447 (Debian DSA-3593-1 : libxml2 - security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 43650 (Juniper Junos Multiple vulnerabilities in libxml2 (JSA10916)).
Upgrading to version 2.9.4 eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (91447). Entries connected to this vulnerability are available at 79335, 79336, 79337 and 79338.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.7VulDB Meta Temp Score: 8.5
VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
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 |
Nessus ID: 91447
Nessus Name: Debian DSA-3593-1 : libxml2 - security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 14611
OpenVAS Name: Amazon Linux Local Check: alas-2016-719
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: libxml2 2.9.4
Patch: git.gnome.org
Timeline
05/02/2016 🔍05/23/2016 🔍
06/02/2016 🔍
06/03/2016 🔍
06/09/2016 🔍
06/09/2016 🔍
06/10/2016 🔍
08/23/2022 🔍
Sources
Advisory: RHSA-2016:1292Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-4447 (🔍)
OVAL: 🔍
SecurityTracker: 1036348
SecurityFocus: 90864 - Libxml2 'xmlParseName' CVE-2016-4447 Remote Denial of Service Vulnerability
See also: 🔍
Entry
Created: 06/10/2016 09:39Updated: 08/23/2022 10:44
Changes: 06/10/2016 09:39 (61), 01/14/2019 08:03 (19), 08/23/2022 10:44 (5)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.