GHSA-j35p-q24r-5367 json
Dep Group Remote Memory Exhaustion (Denial of Service) in ckb
published 4y ago modified 4y ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
### Impact A remote attacker could exploit this vulnerability to exhaust ckb process memory of an affected node.
### Patches Upgrade to 0.43.1 or later.
### References After resolving the outpoints of one dep group, we put the corresponding content into a vec ( https://github.com/nervosnetwork/ckb/blob/v0.42.0/util/types/src/core/cell.rs#L600-L617 ), there is a vulnerability to a memory dos attack because there is no determination of whether the outpoints is duplicated.
PoC: ``` before send dos tx rss: 105700
after rss: 2306932 ```
DoS cost: 25.6 KB * 150 + dep_tx out_points capacity ( 36 * 150 * 100 = 540000 ) = 4380000 CKB Send 50 dos_tx, memory exhausted: (25.6 KB * 150 * 100) * 50 = 19.2 GB
Patch / fix
- crates.io ckb 0.43.1
Is GHSA-j35p-q24r-5367 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | ckb | <0.43.1 |
0.43.1 |
References
Sources
- GitHub Advisory GHSA-j35p-q24r-5367
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.