GHSA-pr39-8257-fxc2
Nervos CKB DoS: Process exists when p2p discovery protocol receives unsupported peer IP
Low
crates.io
- Severity
- Low
- The publisher's own rating, not a CVSS score
- Exploit chance (EPSS)
- —
- No score published
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- —
- Not classified
- Fix
0.34.0- Upgrade ckb to this version or later
Description
The p2p discovery protocol assumes that the peer IP must be valid IPv4 address.
Affected versions
crates.io
| Package | Vulnerable | Fixed in |
|---|---|---|
| ckb | < 0.34.0 |
0.34.0 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
ckb crates.io → 0.34.0
- cargo
cargo update -p ckb --precise 0.34.0
References
Other links
Timeline
- Published
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-29c2-65rj-h343 Nervos CKB Permit load cell data from memory | Medium | Also affects ckb |
| GHSA-h4c3-5275-vrmg Nervos CKB Pool does not remove the conflicting transactions from the statistics | Medium | Also affects ckb |
| GHSA-q73f-w3h7-7wcc Nervos CKB Transaction which calls syscall load_cell_data_hash has nondeterministic result | Critical | Also affects ckb |
| GHSA-3gjh-29fv-8hr6 Nervos CKB Snappy decompress length can be very large and causes out of memory error | High | Also affects ckb |
| GHSA-wjxc-pjx9-4wvm Nervos CKB Panic on malformed input | High | Also affects ckb |
| GHSA-hjqq-29pw-96wj Nervos CKB node panics when processing a block which parent timestamp is too new | High | Also affects ckb |
| GHSA-r9rv-9mh8-pxf4 Nervos CKB BlockTimeTooNew should not be considered as invalid block | Medium | Also affects ckb |
| GHSA-84x2-2qv6-qg56 Nervos CKB P2P DoS Attacks | Critical | Also affects ckb |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor