GHSA-vx9q-rhv9-3jvg
Fix: airlift/aircompressor#309GHSA-vx9q-rhv9-3jvg is a Out-of-bounds Read vulnerability in io.airlift:aircompressor-v3. O3 Security confirms whether GHSA-vx9q-rhv9-3jvg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
aircompressor Snappy and LZ4 Java-based decompressor implementation can leak information from reused output buffer
Real-World Exposure
io.airlift:aircompressor-v3☕io.airlift:aircompressorReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.airlift:aircompressor-v3 | all versions | 3.4 |
| ☕Maven | io.airlift:aircompressor | all versions | 2.0.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.airlift:aircompressor-v3. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update io.airlift:aircompressor-v3 to 3.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vx9q-rhv9-3jvg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-vx9q-rhv9-3jvg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-vx9q-rhv9-3jvg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-vx9q-rhv9-3jvg in your dependencies?
O3 detects GHSA-vx9q-rhv9-3jvg across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.