Application crash via entity-decoding boundary read
Published May 17, 2022 · Updated Aug 3, 2024
Heap out-of-bounds read in ezXML 0.8.6 allows attackers to crash an application when it parses a crafted XML file. After reallocating the entity-expansion buffer, ezxml_decode() calls strchr() from a pointer at the end of the new allocation. The application must parse attacker-controlled XML; the published proof of concept demonstrates a process crash.
Summary
What happened
Heap out-of-bounds read in ezXML 0.8.6 allows attackers to crash an application when it parses a crafted XML file. After reallocating the entity-expansion buffer, ezxml_decode() calls strchr() from a pointer at the end of the new allocation. The application must parse attacker-controlled XML; the published proof of concept demonstrates a process crash.
The record
- CVE
- CVE-2022-30045
- Published
- May 17, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 17, 2022CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- ezxml-poc.xml proof of conceptproof 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