Application crash via unchecked chunk-size allocation
Published Jun 15, 2023 · Updated Feb 13, 2025
Uncontrolled resource consumption in Xerial snappy-java 1.1.10.0 and earlier allows remote attackers to crash applications via crafted streams. SnappyInputStream.hasNextChunk reads a four-byte chunk length and uses it directly to allocate a byte array without validating its sign or size. An embedding application must pass attacker-controlled framed input to SnappyInputStream; a huge positive length exhausts JVM memory, while a negative length raises an unchecked exception.
Summary
What happened
Uncontrolled resource consumption in Xerial snappy-java 1.1.10.0 and earlier allows remote attackers to crash applications via crafted streams. SnappyInputStream.hasNextChunk reads a four-byte chunk length and uses it directly to allocate a byte array without validating its sign or size. An embedding application must pass attacker-controlled framed input to SnappyInputStream; a huge positive length exhausts JVM memory, while a negative length raises an unchecked exception.
The record
- CVE
- CVE-2023-34455
- Published
- Jun 15, 2023
- Updated
- Feb 13, 2025
- Vendor
- Xerial
- Product
- snappy-java
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.1.10.1
What conditions does exploitation require?
What is affected?
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
- GitHub advisory crash reproducerproof 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