What is CVE-2024-36124?

CVE-2024-36124 is a medium-severity out-of-bounds read vulnerability in org.iq80.snappy:snappy (maven), affecting versions < 0.5. It is fixed in 0.5. A read operation accesses a memory location beyond the intended buffer boundary.

How severe is CVE-2024-36124?

CVE-2024-36124 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.iq80.snappy:snappy are affected by CVE-2024-36124?

org.iq80.snappy:snappy (maven) versions < 0.5 is affected.

Is there a fix for CVE-2024-36124?

Yes. CVE-2024-36124 is fixed in 0.5. Upgrade to this version or later.

Is CVE-2024-36124 exploitable, and should I be worried?

Whether CVE-2024-36124 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-36124 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2024-36124 in org.iq80.snappy:snappy

Q: How severe is CVE-2024-36124?

CVE-2024-36124 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of org.iq80.snappy:snappy are affected by CVE-2024-36124?

org.iq80.snappy:snappy (maven) versions < 0.5 is affected.

Q: Is there a fix for CVE-2024-36124?

Yes. CVE-2024-36124 is fixed in 0.5. Upgrade to this version or later.

Q: Is CVE-2024-36124 exploitable, and should I be worried?

Whether CVE-2024-36124 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-36124 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-36124?

Upgrade org.iq80.snappy:snappy to 0.5 or later.

Summary

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

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.

A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.

CVE-2024-36124 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.5); upgrading removes the vulnerable code path.

Affected versions

org.iq80.snappy:snappy (< 0.5)

Security releases

org.iq80.snappy:snappy → 0.5 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade org.iq80.snappy:snappy to 0.5 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-36124? CVE-2024-36124 is a medium-severity out-of-bounds read vulnerability in org.iq80.snappy:snappy (maven), affecting versions < 0.5. It is fixed in 0.5. A read operation accesses a memory location beyond the intended buffer boundary.
How severe is CVE-2024-36124? CVE-2024-36124 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.iq80.snappy:snappy are affected by CVE-2024-36124? org.iq80.snappy:snappy (maven) versions < 0.5 is affected.
Is there a fix for CVE-2024-36124? Yes. CVE-2024-36124 is fixed in 0.5. Upgrade to this version or later.
Is CVE-2024-36124 exploitable, and should I be worried? Whether CVE-2024-36124 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-36124 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-36124? Upgrade org.iq80.snappy:snappy to 0.5 or later.