GHSA-vx9q-rhv9-3jvg: Maven/io.airlift:aircompressor-v3 vulnerability
Summary Incorrect handling of malformed data in Java-based decompressor implementations for Snappy and LZ4 allows remote attackers to read previous buffer contents via crafted compressed input. In applications where the output buffer is reused without being cleared, this may lead to disclosure of sensitive data.
Details With certain crafted compressed inputs, elements from the output buffer can end up in the uncompressed output. 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. This is similar to GHSA-cmp6-m4wj-q63q.
Impact Applications using aircompressor as described above may leak sensitive information to external unauthorized attackers.
Mitigation
The vulnerability is fixed in release 3.4 and 2.0.3. However, it can be mitigated by either: Avoiding reuse of the decompression buffer across calls Clearing the decompression buffer before a call to decompress data
Other sources
Summary Incorrect handling of malformed data in Java-based decompressor implementations for Snappy and LZ4 allows remote attackers to read previous buffer contents via crafted compressed input. In applications where the output buffer is reused without being cleared, this may lead to disclosure of sensitive data.
Details With certain crafted compressed inputs, elements from the output buffer can end up in the uncompressed output. 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. This is similar to GHSA-cmp6-m4wj-q63q.
Impact Applications using aircompressor as described above may leak sensitive information to external unauthorized attackers.
Mitigation
The vulnerability is fixed in release 3.4. However, it can be mitigated by either: Avoiding reuse of the decompression buffer across calls Clearing the decompression buffer before a call to decompress data
— GitHub
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/io.airlift:aircompressor-v3to a version that resolves this vulnerability.Fixed in 3.4 - Upgrade
Upgrade
maven/io.airlift:aircompressorto a version that resolves this vulnerability.Fixed in 2.0.3 - Upgrade
Upgrade
aircompressorto a version that resolves this vulnerability.Fixed in 3.4 - Upgrade
Upgrade
lz4-javato a version that resolves this vulnerability.Fixed in 2.0.3 - Compensating control
Avoid reusing the decompression/output buffer across calls, or clear the buffer before each decompression call.
Event History
Frequently Asked Questions
What is the severity of GHSA-vx9q-rhv9-3jvg?
GHSA-vx9q-rhv9-3jvg is classified as a vulnerability that may lead to information disclosure due to improper handling of malformed data.
How do I fix GHSA-vx9q-rhv9-3jvg?
To fix GHSA-vx9q-rhv9-3jvg, you should upgrade to version 3.4 or later of the io.airlift:aircompressor-v3 package.
Which applications are affected by GHSA-vx9q-rhv9-3jvg?
Applications that use the Java-based decompressor implementations for Snappy and LZ4 are affected by GHSA-vx9q-rhv9-3jvg.
Can GHSA-vx9q-rhv9-3jvg lead to remote attacks?
Yes, GHSA-vx9q-rhv9-3jvg allows remote attackers to read previous buffer contents through crafted compressed input.
What are the potential risks of GHSA-vx9q-rhv9-3jvg?
The potential risks include sensitive data exposure if the output buffer is reused without being cleared.