CVE-2024-36114 Decompressors can crash the JVM and leak memory content in Aircompressor
Attackers can crash the JVM or leak sensitive memory by providing malicious compressed data to the Aircompressor library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-36114?
CVE-2024-36114 is a high-severity memory corruption vulnerability in airlift aircompressor, published on 29 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Aircompressor is a library with ports of the Snappy, LZO, LZ4, and Zstandard compression algorithms to Java. All decompressor implementations of Aircompressor (LZ4, LZO, Snappy, Zstandard) can crash the JVM for certain input, and in some cases also leak the content of other memory of the Java process (which could contain sensitive information). When decompressing certain data, the decompressors try to access memory outside the bounds of the given byte arrays or byte buffers. Because Aircompressor 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. Users should update to Aircompressor 0.27 or newer where these issues have been fixed. When decompressing data from untrusted users, this can be exploited for a denial-of-service attack by crashing the JVM, or to leak other sensitive information from the Java process. There are no known workarounds for this issue.
Which versions are affected by CVE-2024-36114?
2 open source packages ship an affected version, including io.airlift:aircompressor.
| Package | Affected | Fixed in |
|---|---|---|
io.airlift:aircompressor Maven | All versions | 0.27 |
io.airlift:aircompressor Maven | All versions | 0.27 |
How do I fix CVE-2024-36114?
Upgrade io.airlift:aircompressor to 0.27 or later.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2024-36114 being exploited?
There is no known exploitation of CVE-2024-36114 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as CLSA-2026-1788349507, CLSA-2026-1788757894, CLSA-2026-1788757897, CLSA-2026-1788757903, ECHO-422f-d848-6aa6, GHSA-973x-65j7-xcf4 and 2 more.