CVE-2018-12018
Last modified
CVE-2018-12018 is a vulnerability of currently unknown severity. The GetBlockHeadersMsg handler in the LES protocol implementation in Go Ethereum (aka geth) before 1.8.11 may lead to an access violation because of an integer signedness error for the array index, which allows attackers to launch a Denial of Service attack by sending a packet with a -1 query.Skip value. The vulnerable remote node would be crashed by such an attack immediately, aka the EPoD (Ethereum Packet of Death) issue.. EPSS estimates a 4.25% chance of exploitation in the next 30 days.
Description
The GetBlockHeadersMsg handler in the LES protocol implementation in Go Ethereum (aka geth) before 1.8.11 may lead to an access violation because of an integer signedness error for the array index, which allows attackers to launch a Denial of Service attack by sending a packet with a -1 query.Skip value. The vulnerable remote node would be crashed by such an attack immediately, aka the EPoD (Ethereum Packet of Death) issue.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Ethereum | Go Ethereum | < 1.8.11 |
References
- https://github.com/ethereum/go-ethereum/commit/a5237a27eaf81946a3edb4fafe13ed6359d119e4Patch, Third Party Advisory
- https://github.com/ethereum/go-ethereum/pull/16891Issue Tracking, Patch, Third Party Advisory
- https://github.com/ethereum/go-ethereum/releases/tag/v1.8.11Third Party Advisory
- https://peckshield.com/2018/06/27/EPoD/Exploit, Third Party Advisory
- https://github.com/ethereum/go-ethereum/commit/a5237a27eaf81946a3edb4fafe13ed6359d119e4Patch, Third Party Advisory
- https://github.com/ethereum/go-ethereum/pull/16891Issue Tracking, Patch, Third Party Advisory
- https://github.com/ethereum/go-ethereum/releases/tag/v1.8.11Third Party Advisory
- https://peckshield.com/2018/06/27/EPoD/Exploit, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2018-12018?
How severe is CVE-2018-12018?
How do I fix CVE-2018-12018?
Are you affected by CVE-2018-12018?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
