GHSA-ppjg-v974-84cm CVE-2023-40591 GO-2023-2046
Go-Ethereum vulnerable to denial of service via malicious p2p message
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 1.12%
- Chance of exploitation in the next 30 days. Higher than 66.20% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-400 Uncontrolled Resource Consumption
- Fix
1.12.1-stable- Upgrade github.com/ethereum/go-ethereum to this version or later
Description
Impact
A vulnerable node, can be made to consume unbounded amounts of memory when handling specially crafted p2p messages sent from an attacker node.
Details
The p2p handler spawned a new goroutine to respond to ping requests. By flooding a node with ping requests, an unbounded number of goroutines can be created, leading to resource exhaustion and potentially crash due to OOM.
Patches
The fix is included in geth version 1.12.1-stable, i.e, 1.12.2-unstable and onwards.
Fixed by https://github.com/ethereum/go-ethereum/pull/27887
Workarounds
No known workarounds.
Credits
This bug was reported by Patrick McHardy and reported via bounty@ethereum.org.
References
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| github.com/ethereum/go-ethereum | < 1.12.1-stable |
1.12.1-stable |
| github.com/ethereum/go-ethereum | < 1.12.1 |
1.12.1 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
github.com/ethereum/go-ethereum Go → 1.12.1-stable
- go
go get github.com/ethereum/go-ethereum@v1.12.1-stable && go mod tidy
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Weakness
CWE-400: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How to prevent it
- Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
- Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
- Implementation: Ensure that all failures in resource allocation place the system into a safe posture.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-m6j8-rg6r-7mv8 Go Ethereum Improperly Validates the ECIES Public Key in RLPx Handshake | High | Also affects github.com/ethereum/go-ethereum |
| GHSA-2gjw-fg97-vg3r Go Ethereum affected by DoS via malicious p2p message | High | Also affects github.com/ethereum/go-ethereum |
| GHSA-689v-6xwf-5jf3 Go Ethereum affected by DoS via malicious p2p message | High | Also affects github.com/ethereum/go-ethereum |
| GHSA-mq3p-rrmp-79jg go-ethereum is vulnerable to high CPU usage leading to DoS via malicious p2p message | High | Also affects github.com/ethereum/go-ethereum |
| GHSA-mr7q-c9w9-wh4h go-ethereum is vulnerable to DoS via malicious p2p message affecting a vulnerable node | High | Also affects github.com/ethereum/go-ethereum |
| GHSA-q26p-9cq4-7fc2 Go Ethereum vulnerable to DoS via malicious p2p message | Medium | Also affects github.com/ethereum/go-ethereum |
| GHSA-4xc9-8hmq-j652 go-ethereum vulnerable to DoS via malicious p2p message | High | Also affects github.com/ethereum/go-ethereum |
| GHSA-v9jh-j8px-98vq go-ethereum vulnerable to denial of service via crafted GraphQL query | High | Also affects github.com/ethereum/go-ethereum |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor