Skip to content
Fencer Vulns
medium 5.3

CVE-2024-36124 json

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

published 2024-06-03 2 y ago modified 2026-09-10 1 mo ago also GHSA-8wh2-6qhj-h7j9 , EUVD-2024-1986

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 42%
public exploits
0
none known

Summary

iq80 Snappy is a compression/decompression library. 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.

Patch / fix

  • maven org.iq80.snappy:snappy 0.5
  • xerial snappy-java 0.5

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-36124 updated cvss 5.3

snappy: tries to read outside the bounds of the given byte arrays

  • Red Hat A-MQ Clients 2 snappy Red Hat Logging Subsystem for Red Hat OpenShift snappy
    affected: workaround, no fix available
  • Red Hat Migration Toolkit for Applications 6 snappy Red Hat Migration Toolkit for Runtimes snappy Red Hat build of Apache Camel - HawtIO 4 snappy
    affected: workaround, no fix planned “Will not fix”
  • Red Hat build of Apicurio Registry 2 snappy Red Hat build of Debezium 2 snappy
    affected: workaround, no fix available
  • Red Hat build of OptaPlanner 8 snappy Red Hat Data Grid 8 snappy Red Hat Fuse 7 snappy Red Hat Integration Camel K 1 snappy Red Hat JBoss Data Grid 7 snappy Red Hat Process Automation 7 snappy
    +2 more products
    Red Hat Single Sign-On 7 snappy Red Hat streams for Apache Kafka snappy
    affected: workaround, no fix planned “Will not fix”
  • Red Hat Cryostat 2 snappy Red Hat OpenShift Serverless snappy Red Hat AMQ Broker 7 snappy Red Hat AMQ Clients snappy Red Hat Ansible Automation Platform 2 snappy Red Hat build of Apache Camel 4 for Quarkus 3 snappy
    +6 more products
    Red Hat build of Apache Camel for Spring Boot 4 snappy Red Hat Build of Keycloak snappy Red Hat build of Quarkus snappy-java Red Hat JBoss Enterprise Application Platform 7 snappy Red Hat JBoss Enterprise Application Platform 8 snappy Red Hat JBoss Enterprise Application Platform Expansion Pack snappy
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
maven org.iq80.snappy:snappy
<0.5
0.5

Affected products

  • dain snappy
  • xerial snappy-java

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.