Skip to content

DoS via malicious p2p message in Go Ethereum

Moderate severity GitHub Reviewed Published May 11, 2022 in ethereum/go-ethereum • Updated Jan 27, 2023

Package

gomod github.com/ethereum/go-ethereum (Go)

Affected versions

< 1.10.17

Patched versions

1.10.17

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: ethereum/go-ethereum#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:

References

@holiman holiman published to ethereum/go-ethereum May 11, 2022
Published by the National Vulnerability Database May 20, 2022
Published to the GitHub Advisory Database May 24, 2022
Reviewed May 24, 2022
Last updated Jan 27, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(61st percentile)

Weaknesses

Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Learn more on MITRE.

CVE ID

CVE-2022-29177

GHSA ID

GHSA-wjxw-gh3m-7pm5

Source code

github.com/ethereum/go-ethereum
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.