Vulnerability · Published Jun 15, 2023 · Assigned by GitHub_M

CVE-2023-34454snappy-java's Integer Overflow vulnerability in compress leads to DoS

Medium 5.9

In plain English

A medium-severity integer overflow in snappy-java from xerial. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 1.5% (higher than 74% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)5.9Medium
Exploit odds (30 days)1.5%top 26.1% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack toolingNoneno public tooling known

Official description

snappy-java is a fast compressor/decompressor for Java. Due to unchecked multiplications, an integer overflow may occur in versions prior to 1.1.10.1, causing an unrecoverable fatal error. The function `compress(char[] input)` in the file `Snappy.java` receives an array of characters and compresses it. It does so by multiplying the length by 2 and passing it to the rawCompress` function. Since the length is not tested, the multiplication by two can cause an integer overflow and become negative. The rawCompress function then uses the received length and passes it to the natively compiled maxCompressedLength function, using the returned value to allocate a byte array. Since the maxCompressedLength function treats the length as an unsigned integer, it doesn’t care that it is negative, and it returns a valid value, which is casted to a signed integer by the Java engine. If the result is negative, a `java.lang.NegativeArraySizeException` exception will be raised while trying to allocate the array `buf`. On the other side, if the result is positive, the `buf` array will successfully be allocated, but its size might be too small to use for the compression, causing a fatal Access Violation error. The same issue exists also when using the `compress` functions that receive double, float, int, long and short, each using a different multiplier that may cause the same issue. The issue most likely won’t occur when using a byte array, since creating a byte array of size 0x80000000 (or any other negative value) is impossible in the first place. Version 1.1.10.1 contains a patch for this issue.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Mavenorg.xerial.snappy:snappy-java1.1.10.1GHSA-fjpj-2g6w-x25r
Ubuntu:22.04:LTSsnappy-javano fix listedUBUNTU-CVE-2023-34454
Ubuntu:24.04:LTSsnappy-javano fix listedUBUNTU-CVE-2023-34454
Ubuntu:25.10snappy-javano fix listedUBUNTU-CVE-2023-34454
Ubuntu:26.04:LTSsnappy-javano fix listedUBUNTU-CVE-2023-34454
Ubuntu:26.10snappy-javano fix listedUBUNTU-CVE-2023-34454

Affected products (as reported)

VendorProductVersions
xerial snappy-java < 1.1.10.1

Weakness: CWE-190 · Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

References