You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
See doc/triage.md for instructions on how to triage this report.
module: github.com/ethereum/go-ethereum
package: go-ethereum
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.
cves:
- CVE-2022-29177
links:
pr: https://github.com/ethereum/go-ethereum/pull/24507
context:
- https://github.com/ethereum/go-ethereum/security/advisories/GHSA-wjxw-gh3m-7pm5
The text was updated successfully, but these errors were encountered:
CVE-2022-29177 references github.com/ethereum/go-ethereum, which may be a Go module.
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.Links:
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: