CVE-2022-29177

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.

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.

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

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.

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.

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

DoS via malicious p2p message in Go Ethereum in github.com/ethereum/go-ethereum

These are all security issues fixed in the govulncheck-vulndb-0.0.20250807T150727-1.1 package on the GA media of openSUSE Tumbleweed.