How severe is GHSA-3gjh-29fv-8hr6?

No CVSS score has been assigned to GHSA-3gjh-29fv-8hr6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3gjh-29fv-8hr6?

GHSA-3gjh-29fv-8hr6 affects the following packages: ckb (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-3gjh-29fv-8hr6?

Update ckb to 0.34.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3gjh-29fv-8hr6 is resolved across your whole dependency graph.

How do I detect GHSA-3gjh-29fv-8hr6 in my crates.io dependencies?

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

How do I mitigate GHSA-3gjh-29fv-8hr6 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-3gjh-29fv-8hr6?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3gjh-29fv-8hr6 can be triaged on real exposure rather than presence alone.

Is GHSA-3gjh-29fv-8hr6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-3gjh-29fv-8hr6 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-3gjh-29fv-8hr6 published, and has it been updated?

GHSA-3gjh-29fv-8hr6 was published on February 3, 2024. 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

GHSA-3gjh-29fv-8hr6 — ckb

GHSA-3gjh-29fv-8hr6 is a security vulnerability in ckb. A fix is available for ckb — see the affected versions and patch details below.

Nervos CKB Snappy decompress length can be very large and causes out of memory error

Published

Feb 3, 2024

Updated

Feb 3, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Feb 3, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀ckb

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

Impact

Adversary can create message which compressed size is less than the package limit but the decompressed length is very large such as 1G. It will cost the node many memories to process the network messages, and on the system with less than 1G memory, the process is killed directly because of out of memory error.

Patches

The node must check the decompress length before allocating the memory for the message.

References

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`ckb`	all versions	0.34.2`cargo update -p ckb --precise 0.34.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ckb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ckb to 0.34.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3gjh-29fv-8hr6 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-3gjh-29fv-8hr6 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-3gjh-29fv-8hr6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Adversary can create message which compressed size is less than the package limit but the decompressed length is very large such as 1G. It will cost the node many memories to process the network messages, and on the system with less than 1G memory, the process is killed directly because of out of memory error. ### Patches The node must check the decompress length before allocating the memory for the message. ### References * https://github.com/nervosnetwork/ckb/blob/687d797f1888dd05d1f38ce6d1bef3e5b9b6e38b/network/src/compress.rs#L68 * https://github.com/BurntSushi/rust-snappy/

O3 Security · Impact-Aware SCA

Is GHSA-3gjh-29fv-8hr6 in your dependencies?

O3 Security finds GHSA-3gjh-29fv-8hr6 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