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

GHSA-84x2-2qv6-qg56 ckb

Fix: nervosnetwork/ckb@c5eb547

GHSA-84x2-2qv6-qg56 is a security vulnerability in ckb. A fix is available for ckb — see the affected versions and patch details below.

Nervos CKB P2P DoS Attacks

Published
Feb 2, 2024
Updated
Feb 2, 2024
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Feb 2, 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

The P2P protocols lack of rate limit. For example, in relay protocol, when a node receives a broadcasted tx_hashes, it will mark it in memory to avoid duplicated requests. code → .

It is easy to establish a DoS attach by generating random tx hashes.

Impact

It affects all nodes connected to the P2P network.

Workarounds

Apply rate limit on the data sent to CKB P2P port.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.iockball versions0.34.0cargo update -p ckb --precise 0.34.0

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.34.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-84x2-2qv6-qg56 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-84x2-2qv6-qg56 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-84x2-2qv6-qg56. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The P2P protocols lack of rate limit. For example, in relay protocol, when a node receives a broadcasted `tx_hashes`, it will mark it in memory to avoid duplicated requests. [code → ](https://github.com/nervosnetwork/ckb/blob/26e4837212c392c3c706a0da7a056131fb060433/sync/src/relayer/transactions_process.rs#L67). It is easy to establish a DoS attach by generating random tx hashes. ### Impact It affects all nodes connected to the P2P network. ### Workarounds Apply rate limit on the data sent to CKB P2P port.
O3 Security · Impact-Aware SCA

Is GHSA-84x2-2qv6-qg56 in your dependencies?

O3 Security finds GHSA-84x2-2qv6-qg56 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-84x2-2qv6-qg56: ckb DoS | O3 Security