Code execution via entity-node type confusion
Published May 2, 2024 · Updated Nov 25, 2024
Type confusion in libxmljs2 0.35.0 and earlier allows attackers to execute code or crash a process through crafted XML. The namespaces() method passes an entity-declaration grandchild to XmlNode::get_local_namespaces(), which treats it as an incompatible node type. Exploitation requires an application to parse attacker-controlled XML and then call namespaces() on that entity-derived grandchild; consequences include a process crash or code execution.
Summary
What happened
Type confusion in libxmljs2 0.35.0 and earlier allows attackers to execute code or crash a process through crafted XML. The namespaces() method passes an entity-declaration grandchild to XmlNode::get_local_namespaces(), which treats it as an incompatible node type. Exploitation requires an application to parse attacker-controlled XML and then call namespaces() on that entity-derived grandchild; consequences include a process crash or code execution.
The record
- CVE
- CVE-2024-34394
- Published
- May 2, 2024
- Updated
- Nov 25, 2024
- Vendor
- marudor
- Product
- libxmljs2
- Classifications
- CWE-843
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 2, 2024CVE publishedPublication date reported by the CVE source.
- Nov 25, 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=*
- Affected versionversion=0 <=0.33.0
What conditions does exploitation require?
What is affected?
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
- JFrog namespaces() entity-node proof of conceptproof of concept · unverified
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