GHSA-wjxw-gh3m-7pm5
MEDIUMDoS via malicious p2p message in Go Ethereum
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
github.com/ethereum/go-ethereumReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
A vulnerable node, if configured to use high verbosity logging, can be made to crash when handling specially crafted p2p messages sent from an attacker node.
Patches
The following PR addresses the problem: https://github.com/ethereum/go-ethereum/pull/24507
Workarounds
Aside from applying the PR linked above, setting loglevel to default level (INFO) makes the node not vulnerable to this attack.
Credits
This bug was reported by nrv via [email protected], who has gracefully requested that the bounty rewards be donated to Médecins sans frontières.
For more information
If you have any questions or comments about this advisory:
- Open an issue in go-ethereum
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/ethereum/go-ethereum | all versions | 1.10.17 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/ethereum/go-ethereum. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/ethereum/go-ethereum to 1.10.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wjxw-gh3m-7pm5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-wjxw-gh3m-7pm5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-wjxw-gh3m-7pm5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-wjxw-gh3m-7pm5 in your dependencies?
O3 detects GHSA-wjxw-gh3m-7pm5 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.