[GHSA-vx9q-rhv9-3jvg] aircompressor Snappy and LZ4 Java-based decompressor implementation can leak information from reused output buffer

[lhotari]

Updates

• Affected products
• Description

Comments
2.0.3 version was released (https://github.com/airlift/aircompressor/releases/tag/2.0.3) with the fix for 2.0.x versions of aircompressor.

[github]

Hi there @martint! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.

This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

[Copilot]

Pull request overview

Updates the GHSA advisory metadata and narrative to reflect the newly released patched version for the 2.0.x line.

Changes:

• Updated advisory details/mitigation text to mention 2.0.3 as a fixed release
• Updated affected version events to mark 2.0.3 as fixed (instead of last_affected 2.0.2)
• Added database_specific.last_known_affected_version_range for the 2.0.x stream

Comments suppressed due to low confidence (1)

advisories/github-reviewed/2025/12/GHSA-vx9q-rhv9-3jvg/GHSA-vx9q-rhv9-3jvg.json:1

• The affected-version metadata now indicates the vulnerable range ends at 2.0.3 (and even adds last_known_affected_version_range: <= 2.0.2), but the advisory text says the vulnerability is fixed in both 3.4 and 2.0.3. These are inconsistent: either (a) add another affected range covering the 3.x line up to 3.4 (and adjust last_known_affected_version_range accordingly), or (b) if only 2.0.x is affected, remove the 3.4 mention from the narrative.

{

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Typo in the details text: 'fix-sized buffer' should be 'fixed-size buffer'.

Suggested change

"details": "### Summary\nIncorrect 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.\n\n### Details\nWith 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](https://github.com/yawkat/lz4-java/security/advisories/GHSA-cmp6-m4wj-q63q).\n\n### Impact\nApplications using aircompressor as described above may leak sensitive information to external unauthorized attackers.\n\n### Mitigation\n\nThe vulnerability is fixed in release 3.4 and 2.0.3. However, it can be mitigated by either:\n* Avoiding reuse of the decompression buffer across calls\n* Clearing the decompression buffer before a call to decompress data",

"details": "### Summary\nIncorrect 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.\n\n### Details\nWith 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 fixed-size buffer for performance purposes. This is similar to [GHSA-cmp6-m4wj-q63q](https://github.com/yawkat/lz4-java/security/advisories/GHSA-cmp6-m4wj-q63q).\n\n### Impact\nApplications using aircompressor as described above may leak sensitive information to external unauthorized attackers.\n\n### Mitigation\n\nThe vulnerability is fixed in release 3.4 and 2.0.3. However, it can be mitigated by either:\n* Avoiding reuse of the decompression buffer across calls\n* Clearing the decompression buffer before a call to decompress data",