Node crash via invalid Ethash DAG memory read
Published Mar 16, 2022 · Updated Aug 4, 2024
Invalid-memory access in Ethereum Go-Ethereum 1.10.9 and earlier allows remote attackers to crash a node through excessive peer messages. The Ethash DAG-generation path in ethash/algorithm.go reads invalid memory when multiple nodes are driven into DAG generation, raising SIGBUS and terminating the process. Exploitation requires unauthenticated network access to the peer protocol and a message sequence that reaches this path; no data disclosure or modification is reported.
Summary
What happened
Invalid-memory access in Ethereum Go-Ethereum 1.10.9 and earlier allows remote attackers to crash a node through excessive peer messages. The Ethash DAG-generation path in ethash/algorithm.go reads invalid memory when multiple nodes are driven into DAG generation, raising SIGBUS and terminating the process. Exploitation requires unauthenticated network access to the peer protocol and a message sequence that reaches this path; no data disclosure or modification is reported.
The record
- CVE
- CVE-2021-42219
- Published
- Mar 16, 2022
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-400, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 16, 2022CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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