go-ethereum v1.17.8 "Protein Sludge Pack"

What it is

go-ethereum (Geth) v1.17.8, "Protein Sludge Pack," is marked recommended for all users and lists the specific pull requests behind each DoS fix, letting an operator trace individual issues (#35862, #35883, #35859, #35857, #35904, #35856 for eth/snap packet handlers; #35881 for JUMPDEST caching; #35861 for IP verification; #35865 for the BAL-accounts vector; #35863 for the STUN crash) rather than treat the release as a single opaque patch.

Preconditions / Affected

Most of the security fixes only become exploitable once the Amsterdam fork activates — the JUMPDEST caching hardening, the BAL-accounts DoS vector, and the EIP-8070 Sparse Blobpool correctness bug are all explicitly post-Amsterdam concerns. The eth/snap p2p handler hardening and the STUN-server crash are not tied to the fork and apply to any node running the affected handlers now.

What to do

Upgrade to v1.17.8 via the project's standard channels: pre-built binaries, Docker images under ethereum/client-go (tag stable), the Launchpad PPA, or the Homebrew tap. No separate configuration flags or manual mitigation steps are given — the release's own guidance is that this upgrade is recommended for all users, with urgency tied to whether Amsterdam has activated on the network the node tracks. Operators building contract-deployment tooling with abigen should also note it now uses sequential nonces when deploying library dependencies (#35888), which can change deployment transaction ordering.

Caveats

The page gives PR numbers for traceability but no CVE identifiers, severity scores, or technical write-ups of the mechanisms — so the exact exploitation path for each DoS issue (e.g., what malformed packet triggers the eth/snap handler bugs) isn't available from this page alone.