Application crash via out-of-bounds entity-name write
Published Apr 15, 2021 · Updated Aug 3, 2024
Out-of-bounds write in ezXML 0.8.6 allows context-dependent attackers to crash applications that parse a crafted XML file. In ezxml_internal_dtd(), an entity name without whitespace makes strcspn return the remaining buffer length, after which the parser writes a semicolon one byte beyond the memory-mapped input. The application must parse attacker-controlled XML through the memory-mapped file path, and successful exploitation terminates the parsing process.
Summary
What happened
Out-of-bounds write in ezXML 0.8.6 allows context-dependent attackers to crash applications that parse a crafted XML file. In ezxml_internal_dtd(), an entity name without whitespace makes strcspn return the remaining buffer length, after which the parser writes a semicolon one byte beyond the memory-mapped input. The application must parse attacker-controlled XML through the memory-mapped file path, and successful exploitation terminates the parsing process.
The record
- CVE
- CVE-2021-31229
- Published
- Apr 15, 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
- Apr 15, 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
- CVE-2021-31229-OOBW-000.sampleproof 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