Application crash via overflowing BitShuffle size calculation
Published Jun 15, 2023 · Updated Dec 12, 2024
Integer overflow in Xerial snappy-java before 1.1.10.1 allows remote attackers to crash applications via oversized primitive arrays. BitShuffle.shuffle multiplies the input array length by the element width without checking for integer overflow, then allocates and indexes an output array using the wrapped size. Reachability requires a consuming application to pass an attacker-controlled, extremely large primitive array; negative or undersized allocations raise exceptions that terminate the affected execution path.
Summary
What happened
Integer overflow in Xerial snappy-java before 1.1.10.1 allows remote attackers to crash applications via oversized primitive arrays. BitShuffle.shuffle multiplies the input array length by the element width without checking for integer overflow, then allocates and indexes an output array using the wrapped size. Reachability requires a consuming application to pass an attacker-controlled, extremely large primitive array; negative or undersized allocations raise exceptions that terminate the affected execution path.
The record
- CVE
- CVE-2023-34453
- Published
- Jun 15, 2023
- Updated
- Dec 12, 2024
- Vendor
- Xerial
- Product
- snappy-java
- Classifications
- CWE-190, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 15, 2023CVE publishedPublication date reported by the CVE source.
- Dec 12, 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?
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?
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