Service crash via NULL dereference in ezxml_internal_dtd
Published Apr 11, 2021 · Updated Aug 3, 2024
NULL pointer dereference in ezXML 0.8.6 allows remote attackers to cause a service interrupt via crafted XML input. The ezxml_internal_dtd() parser passes a NULL pointer to strcmp() while processing the document's internal DTD, triggering a crash. Exploitation requires an application to parse attacker-supplied XML and user interaction with that parsing workflow; the documented impact is availability loss without data disclosure or modification.
Summary
What happened
NULL pointer dereference in ezXML 0.8.6 allows remote attackers to cause a service interrupt via crafted XML input. The ezxml_internal_dtd() parser passes a NULL pointer to strcmp() while processing the document's internal DTD, triggering a crash. Exploitation requires an application to parse attacker-supplied XML and user interaction with that parsing workflow; the documented impact is availability loss without data disclosure or modification.
The record
- CVE
- CVE-2021-30485
- Published
- Apr 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 11, 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-30485-nullptr-000.sampleproof of concept · unverified
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