CVE-2024-56171: Use After Free
First published: Tue Feb 18 2025(Updated: )
Last updated 25 February 2025
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| libxml2 | <2.12.10>2.13.0<=2.13.6 | |
| debian/libxml2 | <=2.9.10+dfsg-6.7+deb11u4<=2.9.14+dfsg-1.3~deb12u1<=2.12.7+dfsg+really2.9.14-0.2<=2.12.7+dfsg+really2.9.14-0.3 | 2.9.10+dfsg-6.7+deb11u6 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-56171
- https://nvd.nist.gov/vuln/detail/CVE-2024-56171
- https://launchpad.net/bugs/cve/CVE-2024-56171
- https://security-tracker.debian.org/tracker/CVE-2024-56171
- https://ubuntu.com/security/CVE-2024-56171
- https://gitlab.gnome.org/GNOME/libxml2/-/issues/828
- https://www.openwall.com/lists/oss-security/2025/02/18/2
- https://gitlab.gnome.org/GNOME/libxml2/-/commit/5880a9a6bd97c0f9ac8fc4f30110fe023f484746
- https://gitlab.gnome.org/GNOME/libxml2/-/commit/245b70d7d2768572ae1b05b3668ca858b9ec4ed4
- https://security.netapp.com/advisory/ntap-20250328-0010/
- https://access.redhat.com/errata/RHSA-2025:2482
- https://access.redhat.com/errata/RHSA-2025:2483
- https://access.redhat.com/errata/RHSA-2025:2507
- https://access.redhat.com/errata/RHSA-2025:2513
- https://access.redhat.com/errata/RHSA-2025:2654
- https://access.redhat.com/errata/RHSA-2025:2660
- https://access.redhat.com/errata/RHSA-2025:2673
- https://access.redhat.com/errata/RHSA-2025:2678
- https://access.redhat.com/errata/RHSA-2025:2679
- https://access.redhat.com/errata/RHSA-2025:2686
- https://access.redhat.com/errata/RHSA-2025:2701
- https://access.redhat.com/errata/RHSA-2025:3066
- https://access.redhat.com/errata/RHSA-2025:3055
- https://access.redhat.com/errata/RHSA-2025:3059
- https://bugzilla.redhat.com/show_bug.cgi?id=2346416
Frequently Asked Questions
What is the severity of CVE-2024-56171?
CVE-2024-56171 has a high severity due to the potential for exploitation through crafted XML documents.
How do I fix CVE-2024-56171?
To fix CVE-2024-56171, upgrade libxml2 to version 2.12.10 or 2.13.6 or later.
What versions of libxml2 are affected by CVE-2024-56171?
CVE-2024-56171 affects libxml2 versions before 2.12.10 and 2.13.0 through 2.13.5.
Can CVE-2024-56171 be exploited remotely?
Yes, CVE-2024-56171 can be exploited remotely if a vulnerable version processes untrusted XML documents.
What types of applications are at risk from CVE-2024-56171?
Applications that use affected versions of libxml2 for XML processing and validation are at risk from CVE-2024-56171.
- agent/type
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/author
- agent/weakness
- collector/usn-cve
- source/Ubuntu
- collector/nvd-cve
- source/NVD
- agent/severity
- agent/trending
- collector/launchpad-cve
- source/Launchpad
- agent/source
- agent/description
- agent/event
- collector/security-tracker-debian
- source/Debian
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- agent/last-modified-date
- agent/references
- agent/tags
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2024-56171
- vendor/gnome
- canonical/libxml2
- package-manager/debian