snappy-java's Integer Overflow vulnerability in shuffle leads to DoS
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| xerial | snappy-java | affected |
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat AMQ Streams 2.5.0 | |||
| cpe:/a:redhat:amq_streams:2 | RHSA-2023:5165 | 2023-09-14T00:00:00Z | |
| Red Hat build of Quarkus 2.13.9.Final | |||
| org.xerial.snappy/snappy-java:1.1.10.5-redhat-00001 | cpe:/a:redhat:quarkus:2.13::el8 | RHSA-2023:7700 | 2023-12-07T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-1858 | 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 a fatal error. The function `shuffle(int[] input)` in the file `BitShuffle.java` receives an array of integers and applies a bit shuffle on it. It does so by multiplying the length by 4 and passing it to the natively compiled shuffle function. Since the length is not tested, the multiplication by four can cause an integer overflow and become a smaller value than the true size, or even zero or negative. In the case of a negative value, a `java.lang.NegativeArraySizeException` exception will raise, which can crash the program. In a case of a value that is zero or too small, the code that afterwards references the shuffled array will assume a bigger size of the array, which might cause exceptions such as `java.lang.ArrayIndexOutOfBoundsException`. The same issue exists also when using the `shuffle` functions that receive a double, float, long and short, each using a different multiplier that may cause the same issue. Version 1.1.10.1 contains a patch for this vulnerability. |
Github GHSA |
GHSA-pqr6-cmr2-h8hf | snappy-java's Integer Overflow vulnerability in shuffle leads to DoS |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.7% (1.707% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|