Crash via malformed DOCTYPE parsing
Published Apr 16, 2021 · Updated Aug 3, 2024
Out-of-bounds write in ezXML 0.8.6 allows remote attackers to crash applications via crafted XML files when parsed. The ezxml_parse_str() DOCTYPE loop advances past the mmap-created input region when strcspn() finds no closing delimiter, then writes a NUL byte through the invalid pointer. Exploitation requires an application to parse attacker-supplied XML, and the documented consequence is process crash or service interruption.
Summary
What happened
Out-of-bounds write in ezXML 0.8.6 allows remote attackers to crash applications via crafted XML files when parsed. The ezxml_parse_str() DOCTYPE loop advances past the mmap-created input region when strcspn() finds no closing delimiter, then writes a NUL byte through the invalid pointer. Exploitation requires an application to parse attacker-supplied XML, and the documented consequence is process crash or service interruption.
The record
- CVE
- CVE-2021-31347
- Published
- Apr 16, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-91, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 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-31347-OOBRW-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