Service interruption via encoding-name length overflow
Published Feb 18, 2022 · Updated May 5, 2025
Integer overflow in Expat before 2.4.5 allows attackers to cause a service interrupt via a crafted parser encoding name. copyString stores the encoding-name character count in an int, allowing a gigabyte-scale length to wrap before allocation and copying. Triggering requires a 64-bit machine and an embedding application that accepts an attacker-controlled encoding name, which is often hardcoded.
Summary
What happened
Integer overflow in Expat before 2.4.5 allows attackers to cause a service interrupt via a crafted parser encoding name. copyString stores the encoding-name character count in an int, allowing a gigabyte-scale length to wrap before allocation and copying. Triggering requires a 64-bit machine and an embedding application that accepts an attacker-controlled encoding name, which is often hardcoded.
The record
- CVE
- CVE-2022-25314
- Published
- Feb 18, 2022
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-190, T1499.004
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 18, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 2025Record 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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