Missing upper bound check on chunk length in snappy-java
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.7.0 | |||
| cpe:/a:redhat:amq_streams:2 | RHSA-2024:3527 | 2024-05-30T00: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 |
| Red Hat build of Quarkus 3.2.9.Final | |||
| org.xerial.snappy/snappy-java:1.1.10.5-redhat-00001 | cpe:/a:redhat:quarkus:3.2::el8 | RHSA-2023:7612 | 2023-11-30T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-2424 | snappy-java is a Java port of the snappy, a fast C++ compresser/decompresser developed by Google. The SnappyInputStream was found to be vulnerable to Denial of Service (DoS) attacks when decompressing data with a too large chunk size. Due to missing upper bound check on chunk length, an unrecoverable fatal error can occur. All versions of snappy-java including the latest released version 1.1.10.3 are vulnerable to this issue. A fix has been introduced in commit `9f8c3cf74` which will be included in the 1.1.10.4 release. Users are advised to upgrade. Users unable to upgrade should only accept compressed data from trusted sources. |
Github GHSA |
GHSA-55g7-9cwv-5qfv | snappy-java's missing upper bound check on chunk length can lead to Denial of Service (DoS) impact |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.2% (1.211% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|