From bd8a0b55de9d8d70d9491cc4ca16c07cc9656ae9 Mon Sep 17 00:00:00 2001 From: Lari Hotari Date: Tue, 24 Feb 2026 23:18:24 +0200 Subject: [PATCH] Improve GHSA-vx9q-rhv9-3jvg --- .../2025/12/GHSA-vx9q-rhv9-3jvg/GHSA-vx9q-rhv9-3jvg.json | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/advisories/github-reviewed/2025/12/GHSA-vx9q-rhv9-3jvg/GHSA-vx9q-rhv9-3jvg.json b/advisories/github-reviewed/2025/12/GHSA-vx9q-rhv9-3jvg/GHSA-vx9q-rhv9-3jvg.json index deff8bdf5cea6..44cc421c9f500 100644 --- a/advisories/github-reviewed/2025/12/GHSA-vx9q-rhv9-3jvg/GHSA-vx9q-rhv9-3jvg.json +++ b/advisories/github-reviewed/2025/12/GHSA-vx9q-rhv9-3jvg/GHSA-vx9q-rhv9-3jvg.json @@ -7,7 +7,7 @@ "CVE-2025-67721" ], "summary": "aircompressor Snappy and LZ4 Java-based decompressor implementation can leak information from reused output buffer", - "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. 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 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", "severity": [ { "type": "CVSS_V4", @@ -47,11 +47,14 @@ "introduced": "0" }, { - "last_affected": "2.0.2" + "fixed": "2.0.3" } ] } - ] + ], + "database_specific": { + "last_known_affected_version_range": "<= 2.0.2" + } } ], "references": [