Application crash via unchecked malloc result
Published Feb 8, 2021 · Updated Aug 3, 2024
Out-of-bounds write in ezxml_new in ezXML 0.8.6 and earlier allows attackers to crash an application while it opens an XML file. The function passes an unchecked malloc result to memcpy when initializing the entity table, so allocation failure writes through a null destination. Reachability depends on how the application obtains XML input; restrictive memory protection causes a segmentation fault, while embedded layouts can overwrite near-null configuration memory.
Summary
What happened
Out-of-bounds write in ezxml_new in ezXML 0.8.6 and earlier allows attackers to crash an application while it opens an XML file. The function passes an unchecked malloc result to memcpy when initializing the entity table, so allocation failure writes through a null destination. Reachability depends on how the application obtains XML input; restrictive memory protection causes a segmentation fault, while embedded layouts can overwrite near-null configuration memory.
The record
- CVE
- CVE-2021-26222
- Published
- Feb 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 8, 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?
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.
Weakness, pattern, technique
Public exploit references
- temp_1.cur_input crash 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