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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2024-36124: 0.49% estimated exploitation activity in the next 30 days; percentile 41.97 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

4 Jun 2024, 17:38 UTC

Last modified by the source

4 Jun 2024, 17:38 UTC

Source last checked

26 Oct 2026, 16:30 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8wh2-6qhj-h7j9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-36124

Advisory: iq80 Snappy out-of-bounds read when uncompressing data, leading to JVM crash
IDs: CVE-2024-36124, GHSA-8wh2-6qhj-h7j9
Record: https://patchnext.com/advisories/cve-2024-36124 (revision 1, source checked 26 Oct 2026, 16:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.iq80.snappy:snappy 0.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.iq80.snappy:snappy: affected < 0.5; fixed in 0.5

## Suggested inspection (read-only)
- Maven org.iq80.snappy:snappy: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.iq80.snappy:snappy.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8wh2-6qhj-h7j9 (GitHub-reviewed advisory GHSA-8wh2-6qhj-h7j9 lists affected ranges: Maven org.iq80.snappy:snappy >=0 <0.5)

Commands are suggestions: review each one before running it.