Denial of Service Vulnerability in libxml2

libxml2 Updated 02 Oct 2025

Summary

07/04/2015
N/A
Yes i
Unrated
Not published

DSA-3057-2: libxml2 - regression update. Affects libxml2 versions < 2.8.0+dfsg1-7+wheezy4. Fixed in 2.8.0+dfsg1-7+wheezy4. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

libxml2 is a widely used library that provides support for reading, modifying, and writing XML and HTML files. It is an essential component for many applications that deal with XML data. However, a vulnerability has been discovered in libxml2 that can lead to a denial of service attack. This vulnerability allows a remote attacker to cause excessive CPU consumption by providing a specially crafted XML file. Even if entity substitution is disabled, which is the default behavior, the attacker can exploit excessive entity substitutions to overwhelm the parser and cause the application to consume excessive resources.

Vulnerability Detail

The vulnerability, identified as CVE-2014-3660, allows a remote attacker to exploit libxml2's XML parser by providing a malicious XML file. When this file is processed by an application using libxml2, the parser becomes overwhelmed with excessive entity substitutions, leading to a denial of service condition. This vulnerability affects libxml2 versions prior to 2.8.0+dfsg1-7+wheezy4. The impact of this vulnerability can be severe, as it can cause applications to become unresponsive or crash, resulting in service disruption and potential data loss.

How To Fix

Minimum fixed version

2.8.0+dfsg1-7+wheezy4

This is the first release that contains the fix.

sudo apt-get install --only-upgrade libxml2

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

Workaround

There is no known workaround for this vulnerability. It is necessary to apply the recommended fix by upgrading the libxml2 package to the patched version.

Conclusion

The libxml2 library is vulnerable to a denial of service attack that can be triggered by processing a specially crafted XML file. To mitigate this vulnerability, it is crucial to upgrade the libxml2 package to the patched version. There is no known workaround for this issue, so applying the fix is the recommended course of action. For further support and guidance on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for libxml2 →

Share this vulnerability

FAQ

libxml2 is a library that provides support for reading, modifying, and writing XML and HTML files. It is widely used in various applications and programming languages.

The vulnerability allows a remote attacker to cause a denial of service condition by overwhelming the libxml2 parser with excessive entity substitutions. This can lead to application crashes and service disruption.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and Vulert will analyze it for any open-source vulnerabilities, including this one.

No, there is no known workaround for this vulnerability. It is necessary to apply the recommended fix by upgrading the libxml2 package.

For further support on vulnerability remediation, you can contact info@devnack.com. They can provide guidance and assistance in addressing this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for libxml2.

How To Fix

Minimum fixed version

2.8.0+dfsg1-7+wheezy4

This is the first release that contains the fix.

sudo apt-get install --only-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