Service interruption via unreleased parser allocations
Published May 26, 2022 · Updated Aug 4, 2024
Memory leaks in Mini-XML 3.2 allow remote attackers to interrupt services that repeatedly process attacker-controlled XML. The reported paths allocate serialized strings and XML element nodes without releasing them before the processing cycle ends. Network reachability requires a consuming application to pass remote XML to the library, and testing did not consistently reproduce the leak in 3.2.
Summary
What happened
Memory leaks in Mini-XML 3.2 allow remote attackers to interrupt services that repeatedly process attacker-controlled XML. The reported paths allocate serialized strings and XML element nodes without releasing them before the processing cycle ends. Network reachability requires a consuming application to pass remote XML to the library, and testing did not consistently reproduce the leak in 3.2.
The record
- CVE
- CVE-2021-42859
- Published
- May 26, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-772, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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
No public exploit references are available in this record.
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