Process crash via failed allocation during DTD copying
Published Oct 6, 2023 · Updated Nov 3, 2025
Use-after-free in GNOME libxml2 2.11.5 and earlier allows remote attackers to crash an application that processes crafted XML. During DTD copying, xmlStaticCopyNodeList assigns the copied DTD to doc->intSubset before copying finishes; an allocation-error cleanup frees that DTD but leaves the document pointer dangling for xmlUnlinkNode to access. Reachability requires DTD copying, user interaction, and a separate memory-allocation failure; the bounded impact is a process crash.
Summary
What happened
Use-after-free in GNOME libxml2 2.11.5 and earlier allows remote attackers to crash an application that processes crafted XML. During DTD copying, xmlStaticCopyNodeList assigns the copied DTD to doc->intSubset before copying finishes; an allocation-error cleanup frees that DTD but leaves the document pointer dangling for xmlUnlinkNode to access. Reachability requires DTD copying, user interaction, and a separate memory-allocation failure; the bounded impact is a process crash.
The record
- CVE
- CVE-2023-45322
- Published
- Oct 6, 2023
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 6, 2023CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- xmllint allocation-failure reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo