Skip to content

iq80 Snappy out-of-bounds read when uncompressing data, leading to JVM crash

Moderate severity GitHub Reviewed Published Jun 1, 2024 in dain/snappy • Updated Jun 4, 2024

Package

maven org.iq80.snappy:snappy (Maven)

Affected versions

< 0.5

Patched versions

0.5

Description

Summary

iq80 Snappy performs out-of-bounds read access when uncompressing certain data, which can lead to a JVM crash.

Details

When uncompressing certain data, Snappy tries to read outside the bounds of the given byte arrays. Because Snappy uses the JDK class sun.misc.Unsafe to speed up memory access, no additional bounds checks are performed and this has similar security consequences as out-of-bounds access in C or C++, namely it can lead to non-deterministic behavior or crash the JVM.

iq80 Snappy is not actively maintained anymore. As quick fix users can upgrade to version 0.5, but in the long term users should prefer migrating to the Snappy implementation in https://github.com/airlift/aircompressor (version 0.27 or newer).

Impact

When uncompressing data from untrusted users, this can be exploited for a denial-of-service attack by crashing the JVM.

References

@dain dain published to dain/snappy Jun 1, 2024
Published by the National Vulnerability Database Jun 3, 2024
Published to the GitHub Advisory Database Jun 4, 2024
Reviewed Jun 4, 2024
Last updated Jun 4, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS score

0.043%
(10th percentile)

Weaknesses

CVE ID

CVE-2024-36124

GHSA ID

GHSA-8wh2-6qhj-h7j9

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.