CVE-2023-34454
MediumCVSS 5.9Exploitation Probability (EPSS)
Elevated risk70th percentile - higher than 70% of all known CVEs
Summary
The snappy-java library has an issue with unchecked multiplications that may lead to integer overflow in versions prior to 1.1.10.1. The `compress(char[] input)` function does not check the length of the array, which can result in critical errors.
Risk Assessment
Organizations may encounter unrecoverable fatal errors that could lead to application crashes using this library. Potential memory allocation issues may result in access violations.
Recommendation
It is recommended to upgrade to version 1.1.10.1 or later to mitigate this vulnerability. A code audit should also be conducted to ensure that array lengths are properly validated before use.
Original NVD description (English source)
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.