Memory corruption via dangling XInclude entity pointers
Published May 18, 2021 · Updated Aug 3, 2024
Use-after-free in XInclude processing in XMLSoft libxml2 before 2.9.11 allows attackers to corrupt memory via crafted XML. xmlXIncludeDoProcess descends into entity-reference nodes whose pointers can be left dangling when DTD data is removed, then scans or modifies freed structures. Exploitation requires XInclude processing after DTD removal, including xmllint with --xinclude and --dropdtd; the stale access can crash the process or corrupt its memory.
Summary
What happened
Use-after-free in XInclude processing in XMLSoft libxml2 before 2.9.11 allows attackers to corrupt memory via crafted XML. xmlXIncludeDoProcess descends into entity-reference nodes whose pointers can be left dangling when DTD data is removed, then scans or modifies freed structures. Exploitation requires XInclude processing after DTD removal, including xmllint with --xinclude and --dropdtd; the stale access can crash the process or corrupt its memory.
The record
- CVE
- CVE-2021-3518
- Published
- May 18, 2021
- Updated
- Aug 3, 2024
- Vendor
- XMLSoft
- Product
- libxml2
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 18, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=libxml2 2.9.11
What conditions does exploitation require?
What is affected?
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.
Public exploit references
No public exploit references are available in this record.
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