Aircompressor's Snappy and LZ4 Java-based decompressor implementation can leak information from reused output buffer
airlift aircompressor
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| io.airlift:aircompressor-v3 Maven |
|
|
| io.airlift:aircompressor Maven |
|
|
airlift aircompressor
| Product | Affected | Fixed in |
|---|---|---|
| io.airlift:aircompressor-v3 Maven |
|
|
| io.airlift:aircompressor Maven |
|
|
Aircompressor is a library with ports of the Snappy, LZO, LZ4, and Zstandard compression algorithms to Java. In versions 3.3 and below, incorrect handling of malformed data in Java-based decompressor implementations for Snappy and LZ4 allow remote attackers to read previous buffer contents via crafted compressed input. With certain crafted compressed inputs, elements from the output buffer can end up in the uncompressed output, potentially leaking sensitive data. This is relevant for applications that reuse the same output buffer to uncompress multiple inputs. This can be the case of a web server that allocates a fix-sized buffer for performance purposes. There is similar vulnerability in GHSA-cmp6-m4wj-q63q. This issue is fixed in version 3.4.
From the CVE record · GitHub_M
The Java-based Snappy and LZ4 decompressors can mishandle malformed compressed data. A remote attacker can use crafted input to expose previous buffer contents in the decompressed output when an application reuses its output buffer across inputs. The input does not specify whether authentication or user interaction is required.
Check applications using Maven io.airlift:aircompressor-v3 before 3.4 or io.airlift:aircompressor before 2.0.3, particularly those that reuse decompression output buffers.