Node crash via unbounded P2P ping goroutines
Published Sep 6, 2023 · Updated Sep 26, 2024
Uncontrolled resource consumption in Ethereum Foundation go-ethereum 1.10.0 through 1.12.0 allows remote attackers to crash nodes via P2P ping floods. The P2P peer handler starts a new goroutine for every inbound ping and sends each pong independently, allowing a peer to create workers without a bound. Any unauthenticated peer that completes a P2P connection can exhaust node memory and trigger an out-of-memory crash; confidentiality and integrity are unaffected.
Summary
What happened
Uncontrolled resource consumption in Ethereum Foundation go-ethereum 1.10.0 through 1.12.0 allows remote attackers to crash nodes via P2P ping floods. The P2P peer handler starts a new goroutine for every inbound ping and sends each pong independently, allowing a peer to create workers without a bound. Any unauthenticated peer that completes a P2P connection can exhaust node memory and trigger an out-of-memory crash; confidentiality and integrity are unaffected.
The record
- CVE
- CVE-2023-40591
- Published
- Sep 6, 2023
- Updated
- Sep 26, 2024
- Vendor
- Ethereum Foundation
- Product
- go-ethereum
- Classifications
- CWE-400, T1499.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 6, 2023CVE publishedPublication date reported by the CVE source.
- Sep 26, 2024Record 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 <1.12.1-stable
- Affected versionversion=< 1.12.1-stable
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