Denial of Service Vulnerability in libxml2: Remote Attack via XML Document

libxml2 Updated 02 Oct 2025

Summary

11/04/2017
N/A
Yes i
Medium
4.7

ALPINE-CVE-2017-5969: 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. Affects libxml2 versions < 2.9.4-r4. Fixed in 2.9.4-r4. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

libxml2 is a widely used XML parsing library that provides a range of functionalities for processing XML documents. It is known for its performance and compliance with various XML standards. However, it has a vulnerability that can be exploited when used in recover mode, which is intended for manual recovery of XML documents. This mode can lead to security issues if not handled properly, making it susceptible to crafted XML documents that can cause denial of service.

Vulnerability Detail

The vulnerability identified as CVE-2017-5969 in libxml2 version 2.9.4 allows remote attackers to exploit the recover mode of the library. By sending a specially crafted XML document, an attacker can trigger a NULL pointer dereference, leading to a denial of service condition. This vulnerability arises from improper handling of XML parsing in recover mode, which should only be used for manual recovery. The CVSS score for this vulnerability is 4.7, indicating a moderate severity level.

How To Fix

Minimum fixed version

2.9.4-r4

This is the first release that contains the fix.

sudo apk add --upgrade libxml2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If you cannot update the package immediately, consider disabling the recover mode when parsing XML documents to mitigate the risk of exploitation. This can be done by ensuring that your application does not invoke the recover mode functionality.

Conclusion

In summary, CVE-2017-5969 is a denial of service vulnerability in libxml2 that can be exploited through crafted XML documents in recover mode. It is crucial to update to the patched version or disable recover mode to mitigate risks associated with this vulnerability.

See every vulnerability recorded for libxml2 →

Share this vulnerability

FAQ

CVE-2017-5969 is a vulnerability in libxml2 that allows remote attackers to cause a denial of service via a crafted XML document when the library is used in recover mode.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The CVSS score of this vulnerability is 4.7, indicating a moderate severity level.

If you cannot update libxml2, ensure that recover mode is disabled in your application to mitigate the risk of exploitation.

The potential impact of this vulnerability is a denial of service, which can disrupt the availability of applications relying on libxml2 for XML processing.

Related vulnerabilities

Recent vulnerabilities recorded for libxml2.

How To Fix

Minimum fixed version

2.9.4-r4

This is the first release that contains the fix.

sudo apk add --upgrade libxml2

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback