Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🦀 crates.io
Not in CISA KEV

GHSA-29c2-65rj-h343 ckb

Fix: nervosnetwork/ckb@2770618

GHSA-29c2-65rj-h343 is a security vulnerability in ckb. A fix is available for ckb — see the affected versions and patch details below.

Nervos CKB Permit load cell data from memory

Published
Feb 3, 2024
Updated
Feb 3, 2024
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed
Exploitation data as of Feb 3, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

5 pkgs affected
🦀ckb🦀ckb🦀ckb🦀ckb🦀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

The faulty nodes will reject transactions which calls load_cell_data syscall but the input cell is still in the mempool. They also ban other nodes and cause the network separation.

Patches

0.35.2, 0.36.1, 0.37.1, 0.38.2

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.iockb0.39.0-rc1&&< 0.39.00.39.0cargo update -p ckb --precise 0.39.0
🦀crates.iockb0.35.0-rc1&&< 0.35.20.35.2cargo update -p ckb --precise 0.35.2
🦀crates.iockb0.36.0-rc1&&< 0.36.10.36.1cargo update -p ckb --precise 0.36.1
🦀crates.iockb0.37.0-rc1&&< 0.37.10.37.1cargo update -p ckb --precise 0.37.1
🦀crates.iockb0.38.0-rc1&&< 0.38.20.38.2cargo update -p ckb --precise 0.38.2

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

    Update ckb to 0.39.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-29c2-65rj-h343 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-29c2-65rj-h343 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-29c2-65rj-h343. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact The faulty nodes will reject transactions which calls `load_cell_data` syscall but the input cell is still in the mempool. They also ban other nodes and cause the network separation. ### Patches 0.35.2, 0.36.1, 0.37.1, 0.38.2
O3 Security · Impact-Aware SCA

Is GHSA-29c2-65rj-h343 in your dependencies?

O3 Security finds GHSA-29c2-65rj-h343 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-29c2-65rj-h343: ckb | O3 Security