How severe is GHSA-wjxc-pjx9-4wvm?

No CVSS score has been assigned to GHSA-wjxc-pjx9-4wvm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wjxc-pjx9-4wvm?

GHSA-wjxc-pjx9-4wvm affects the following packages: ckb (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-wjxc-pjx9-4wvm?

Update ckb to 0.34.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wjxc-pjx9-4wvm is resolved across your whole dependency graph.

How do I detect GHSA-wjxc-pjx9-4wvm 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-wjxc-pjx9-4wvm 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.

Is GHSA-wjxc-pjx9-4wvm actively exploited in the wild?

No public exploit code has been indexed for GHSA-wjxc-pjx9-4wvm 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-wjxc-pjx9-4wvm published, and has it been updated?

GHSA-wjxc-pjx9-4wvm 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

Nervos CKB Panic on malformed inputGHSA-wjxc-pjx9-4wvm

GHSA-wjxc-pjx9-4wvm is a security vulnerability in ckb. A fix is available for ckb — see the affected versions and patch details below.

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

CKB process will panic when received malformed p2p message because of snappy, which is used to compress network messages

References

https://github.com/BurntSushi/rust-snappy/issues/29

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-wjxc-pjx9-4wvm 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.

Frequently Asked Questions

### Impact CKB process will panic when received malformed p2p message because of snappy, which is used to compress network messages ### References https://github.com/BurntSushi/rust-snappy/issues/29

O3 Security · Impact-Aware SCA

Is GHSA-wjxc-pjx9-4wvm in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works