libxml2 2.9.4 Recover Mode XML Document null pointer dereference ⚔ [Disputed]

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

Summaryinfo

A vulnerability, which was classified as problematic, has been found in libxml2 2.9.4. This vulnerability affects unknown code of the component Recover Mode. Performing a manipulation as part of XML Document results in null pointer dereference. This vulnerability is reported as CVE-2017-5969. The attack requires a local approach. No exploit exists. The actual existence of this vulnerability is currently in question. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in libxml2 2.9.4 (Document Processing Software). This affects an unknown functionality of the component Recover Mode. The manipulation as part of a XML Document leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability. The summary by CVE is:

** DISPUTED ** libxml2 2.9.4, when used in recover mode, allows remote attackers to cause a denial of service (NULL pointer dereference) via a crafted XML document. NOTE: The maintainer states "I would disagree of a CVE with the Recover parsing option which should only be used for manual recovery at least for XML parser."

The bug was discovered 03/23/2017. The weakness was disclosed 04/11/2017 by Henri Salo (oss-sec). The advisory is shared at openwall.com. This vulnerability is uniquely identified as CVE-2017-5969 since 02/12/2017. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

The vulnerability was handled as a non-public zero-day exploit for at least 19 days. During that time the estimated underground price was around $0-$5k. The real existence of this vulnerability is still doubted at the moment. The vulnerability scanner Nessus provides a plugin with the ID 99491 (Fedora 25 : libxml2 (2017-a3a47973eb)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 170120 (SUSE Enterprise Linux Security Update for libxml2 (SUSE-SU-2017:1670-1)).

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 Tenable (99491) and SecurityFocus (BID 96188†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.2
VulDB Meta Temp Score: 4.2

VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 4.7
NVD Vector: 🔍

CNA Base Score: 4.7
CNA Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 99491
Nessus Name: Fedora 25 : libxml2 (2017-a3a47973eb)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

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/08/2017 🔍
02/12/2017 +4 days 🔍
03/23/2017 +39 days 🔍
04/11/2017 +19 days 🔍
04/11/2017 +0 days 🔍
04/12/2017 +1 days 🔍
04/19/2017 +7 days 🔍
04/20/2017 +1 days 🔍
08/05/2024 +2664 days 🔍

Sourcesinfo

Advisory: FEDORA-2017-a3a47973eb
Researcher: Henri Salo
Status: Not defined
Disputed: 🔍

CVE: CVE-2017-5969 (🔍)
GCVE (CVE): GCVE-0-2017-5969
GCVE (VulDB): GCVE-100-99597
SecurityFocus: 96188 - libxml2 CVE-2017-5969 Null Pointer Dereference Denial of Service Vulnerability
OSVDB: - CVE-2017-5969 - libxml2 - Denial of Service Issue

Entryinfo

Created: 04/12/2017 10:08
Updated: 08/05/2024 21:17
Changes: 04/12/2017 10:08 (74), 08/29/2020 10:01 (7), 11/28/2022 10:47 (4), 11/28/2022 10:52 (1), 08/05/2024 21:17 (26)
Complete: 🔍
Cache ID: 216:8B3:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!