How severe is GHSA-9q5j-jm53-v7vr?

GHSA-9q5j-jm53-v7vr has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-9q5j-jm53-v7vr?

GHSA-9q5j-jm53-v7vr affects the following packages: lz4-sys (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-9q5j-jm53-v7vr?

Update lz4-sys to 1.9.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9q5j-jm53-v7vr is resolved across your whole dependency graph.

How do I detect GHSA-9q5j-jm53-v7vr in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lz4-sys, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-9q5j-jm53-v7vr if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-9q5j-jm53-v7vr?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9q5j-jm53-v7vr can be triaged on real exposure rather than presence alone.

Is GHSA-9q5j-jm53-v7vr actively exploited in the wild?

No public exploit code has been indexed for GHSA-9q5j-jm53-v7vr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-9q5j-jm53-v7vr published, and has it been updated?

GHSA-9q5j-jm53-v7vr was published on September 1, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀

🦀 crates.io

Not in CISA KEV

CRITICAL severity

GHSA-9q5j-jm53-v7vr — lz4-sys

CRITICALFix: lz4/lz4#972

GHSA-9q5j-jm53-v7vr is a critical-severity (CVSS 9.8) remote code execution vulnerability in lz4-sys. A fix is available for lz4-sys — see the affected versions and patch details below.

lz4-sys vulnerable to memory corruption via issue in liblz4

Also known asRUSTSEC-2022-0051

Published

Sep 1, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀lz4-sys

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

lz4-sys up to v1.9.3 bundles a version of liblz4 that is vulnerable to CVE-2021-3520.

Attackers could craft a payload that triggers an integer overflow upon decompression, causing an out-of-bounds write.

The flaw has been corrected in version v1.9.4 of liblz4, which is included in lz4-sys 1.9.4.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`lz4-sys`	all versions	1.9.4`cargo update -p lz4-sys --precise 1.9.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for lz4-sys, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update lz4-sys to 1.9.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9q5j-jm53-v7vr 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-9q5j-jm53-v7vr can be triaged on real exposure rather than presence alone.

Tailored to GHSA-9q5j-jm53-v7vr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

lz4-sys up to v1.9.3 bundles a version of liblz4 that is vulnerable to [CVE-2021-3520](https://nvd.nist.gov/vuln/detail/CVE-2021-3520). Attackers could craft a payload that triggers an integer overflow upon decompression, causing an out-of-bounds write. The flaw has been corrected in version v1.9.4 of liblz4, which is included in lz4-sys 1.9.4.

O3 Security · Impact-Aware SCA

Is GHSA-9q5j-jm53-v7vr in your dependencies?

O3 Security finds GHSA-9q5j-jm53-v7vr across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works