# CVE-2022-29177: DoS via malicious p2p message in Go-Ethereum

> An attacker can crash a Go-Ethereum node by sending malicious p2p messages if high verbosity logging is enabled.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 May 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-wjxw-gh3m-7pm5, GO-2022-0456

## What is CVE-2022-29177?

CVE-2022-29177 is a medium-severity denial of service vulnerability in go-ethereum, published on 20 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Go Ethereum is the official Golang implementation of the Ethereum protocol. Prior to version 1.10.17, 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. Version 1.10.17 contains a patch that addresses the problem. As a workaround, setting loglevel to default level (`INFO`) makes the node not vulnerable to this attack.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2022-29177?

3 open source packages ship an affected version, including github.com/ethereum/go-ethereum. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/ethereum/go-ethereum` | Go | All versions | 1.10.17 |
| `github.com/ethereum/go-ethereum` | Go | All versions | 1.10.17 |
| `github.com/ethereum/go-ethereum` | Go | All versions | 1.10.17 |

Products: Ethereum Go Ethereum.

## How do I fix CVE-2022-29177?

Upgrade github.com/ethereum/go-ethereum to 1.10.17 or later.

## Is CVE-2022-29177 being exploited?

There is no known exploitation of CVE-2022-29177 in the wild and no public exploit code.

## Other vulnerabilities in go-ethereum

- [CVE-2026-26314](https://insights.sbomify.com/CVE-2026-26314/): Go Ethereum affected by DoS via malicious p2p message (high 8.7)
- [CVE-2023-42319](https://insights.sbomify.com/CVE-2023-42319/): go-ethereum vulnerable to denial of service via crafted GraphQL query (high 7.5)
- [CVE-2023-40591](https://insights.sbomify.com/CVE-2023-40591/): Denial of service via malicious p2p message in go-ethereum (high 7.5)
- [CVE-2021-42219](https://insights.sbomify.com/CVE-2021-42219/): Denial of service in go-ethereum (high 7.5)
- [CVE-2022-23327](https://insights.sbomify.com/CVE-2022-23327/): Denial of Service in Go-Ethereum (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29177 and fix it if it is affected.

What it is: CVE-2022-29177 is a medium-severity denial of service vulnerability in go-ethereum, published on 20 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-29177 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/ethereum/go-ethereum (Go): affected all versions; fixed in 1.10.17
- github.com/ethereum/go-ethereum (Go): affected all versions; fixed in 1.10.17
- github.com/ethereum/go-ethereum (Go): affected all versions; fixed in 1.10.17

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-29177/ (Markdown: https://insights.sbomify.com/CVE-2022-29177/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-29177
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-29177
- OSV: https://osv.dev/vulnerability/CVE-2022-29177

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-29177/
Summaries are generated and may contain mistakes; the official description above is the record.