Node crash via unchecked trie path handling
Published Oct 26, 2021 · Updated Aug 4, 2024
Improper input validation in Geth before 1.10.9 allows remote attackers with a snap/1 peer connection to crash the node. The snap request handler passes a nonexistent trie path to trie.TryGetNode, which reaches path completion with a nil node before the old nil case can run. The peer must negotiate snap/1 and send a crafted GetTrieNodes request; the demonstrated consequence is a process panic and node outage.
Summary
What happened
Improper input validation in Geth before 1.10.9 allows remote attackers with a snap/1 peer connection to crash the node. The snap request handler passes a nonexistent trie path to trie.TryGetNode, which reaches path completion with a nil node before the old nil case can run. The peer must negotiate snap/1 and send a crafted GetTrieNodes request; the demonstrated consequence is a process panic and node outage.
The record
- CVE
- CVE-2021-41173
- Published
- Oct 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- Ethereum Foundation
- Product
- go-ethereum
- Classifications
- T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 26, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.10.9
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