GHSA-p2gm-ffr3-w2xw — ckb
GHSA-p2gm-ffr3-w2xw is a security vulnerability in ckb. A fix is available for ckb — see the affected versions and patch details below.
Nervos CKB vulnerable to low-resource flood DDoS attacks through network message
Real-World Exposure
ckbReal-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
Workarounds
- forbid request genesis through network request
- forbid requesting duplicate data through network request
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | ckb | all versions | 0.101.4cargo update -p ckb --precise 0.101.4 |
Detection & mitigation playbook
Open-source dependencyDetect
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.101.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p2gm-ffr3-w2xw 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-p2gm-ffr3-w2xw can be triaged on real exposure rather than presence alone.
Tailored to GHSA-p2gm-ffr3-w2xw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-p2gm-ffr3-w2xw in your dependencies?
O3 Security finds GHSA-p2gm-ffr3-w2xw across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.