Skip to content
Fencer Intel
medium 5.7

CVE-2021-41173 json

DoS via maliciously crafted p2p message

published 5y ago modified 4mo ago also GHSA-59hh-656j-3p7v , GO-2022-0256 , EUVD-2021-2158

cvss
5.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

Go Ethereum is the official Golang implementation of the Ethereum protocol. Prior to version 1.10.9, a vulnerable node is susceptible to crash when processing a maliciously crafted message from a peer. Version v1.10.9 contains patches to the vulnerability. There are no known workarounds aside from upgrading.

Patch / fix

  • go github.com/ethereum/go-ethereum 1.10.9
  • ethereum go_ethereum 1.10.9

Is CVE-2021-41173 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.24% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 3.5 AV:N/AC:M/Au:S/C:N/I:N/A:P
GitHub 3.1 5.7 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/ethereum/go-ethereum
<1.10.9
1.10.9

Affected products

  • ethereum go-ethereum

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.