Memory overwrite via unchecked allocation failure
Published Feb 8, 2021 · Updated Aug 3, 2024
Out-of-bounds write in ezxml 0.8.6 and earlier allows context-dependent attackers to crash a process or overwrite memory during XML processing. ezxml_toxml passes malloc's unchecked return value directly to strcpy, which writes through a null pointer after allocation failure. A consuming application must process an attacker-influenced XML file and exhaust the memory pool; restrictive systems crash, while some embedded systems permit near-null configuration overwrite.
Summary
What happened
Out-of-bounds write in ezxml 0.8.6 and earlier allows context-dependent attackers to crash a process or overwrite memory during XML processing. ezxml_toxml passes malloc's unchecked return value directly to strcpy, which writes through a null pointer after allocation failure. A consuming application must process an attacker-influenced XML file and exhaust the memory pool; restrictive systems crash, while some embedded systems permit near-null configuration overwrite.
The record
- CVE
- CVE-2021-26220
- Published
- Feb 8, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- 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.
Public exploit references
- ezXML bug 23 ErrorSanitizer 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