Peer-node crash via unbounded stream allocations
Published Dec 7, 2022 · Updated Apr 23, 2025
Uncontrolled resource consumption in rust-libp2p before 0.45.1 allows remote attackers to crash peer nodes via stream requests. Stream handling accepts unlimited concurrent streams and buffers partial payloads without sufficient back pressure, multiplying small allocations until memory is exhausted. Any unauthenticated network peer can repeat these actions until the operating system kills the victim process, interrupting the node.
Summary
What happened
Uncontrolled resource consumption in rust-libp2p before 0.45.1 allows remote attackers to crash peer nodes via stream requests. Stream handling accepts unlimited concurrent streams and buffers partial payloads without sufficient back pressure, multiplying small allocations until memory is exhausted. Any unauthenticated network peer can repeat these actions until the operating system kills the victim process, interrupting the node.
The record
- CVE
- CVE-2022-23486
- Published
- Dec 7, 2022
- Updated
- Apr 23, 2025
- Vendor
- libp2p
- Product
- rust-libp2p
- Classifications
- CWE-770, CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 7, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.45.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo