dbcve.org
SnappyApplication · Dain

CVE-2024-36124

MEDIUM · 5.3 CVSS v3.1 Published 2024-06-03
Fix available
A fix is available. Upgrade to 0.5 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

iq80 Snappy compression library performs out-of-bounds reads during decompression of certain data. The library uses sun.misc.Unsafe for performance optimization, which skips Java array bounds checks, creating similar security risks to C/C++ out-of-bounds memory access. This can lead to non-deterministic behavior or JVM crashes.

MitigationUpgrade iq80 Snappy to version 0.5. Since the library is unmaintained, consider migrating to an actively maintained alternative compression library if long-term support is needed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SnappyApplication
Affected:< 0.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate snappy library files
    Search for snappy JAR files (snappy-java-*.jar, snappy-*.jar) or native libraries (libsnappy*, snappy.dll) in your application directories, lib folder, classpath, or Maven/Gradle local repository
    Affected if iq80 Snappy library files are found in the environment
  2. Identify the exact version
    Check the version from the JAR filename, META-INF/MANIFEST.MF inside the JAR, or your dependency management file (pom.xml, build.gradle, requirements.txt)
    Affected if The version is lower than 0.5 or no version is specified with snappy-java < 0.5
  3. Check dependency declarations
    Inspect your build configuration (pom.xml, build.gradle, package.json, or similar) for direct or transitive dependencies on 'snappy-java', 'iq80-snappy', or 'org.xerial.snappy'
    Affected if A dependency on snappy-java with version < 0.5 is declared
  4. Verify runtime presence
    At runtime, enumerate loaded JARs via ClassLoader.getResources("org/iq80/snappy/Snappy.java") or similar to confirm the library is actually loaded and in use
    Affected if The library is loaded and version cannot be determined or is < 0.5
  5. Confirm usage of unsafe decompression
    Monitor application for calls to Snappy.uncompress(), Snappy.uncompressByteBuffer(), or similar decompression methods from the iq80 Snappy API
    Affected if The vulnerable decompression methods are being called with untrusted input

You are affected if the iq80 Snappy library version is below 0.5 and your application performs decompression operations with data from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.5 or later
Fixed in 0.5
Interim mitigation

Upgrade iq80 Snappy to version 0.5. Since the library is unmaintained, consider migrating to an actively maintained alternative compression library if long-term support is needed.

Recommended fix High confidence

version 0.5

  1. If using Maven, update the dependency in pom.xml: change version from older than 0.5 to 0.5 (e.g., <groupId>org.iq80</groupId><artifactId>snappy</artifactId><version>0.5</version>)
  2. If using Gradle, update build.gradle: change snappy version to '0.5' (e.g., implementation 'org.iq80:snappy:0.5')
  3. If using direct JAR inclusion, download snappy-0.5.jar from the GitHub releases and replace the older JAR in your classpath
  4. Rebuild and test your application to verify the upgrade does not introduce regressions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Snappy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36124 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36124 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data