Vulnerability in github.com/ethereum/go-ethereum (CVE-2020-26241)
Summary
Vulnerability in github.com/ethereum/go-ethereum (CVE-2020-26241). Data can be tampered with by attackers. Mitigation: upgrade to 1.9.17 or later.
Original description
The description as published by the source.
Go Ethereum, or "Geth", is the official Golang implementation of the Ethereum protocol. This is a Consensus vulnerability in Geth before version 1.9.17 which can be used to cause a chain-split where vulnerable nodes reject the canonical chain. Geth's pre-compiled dataCopy (at 0x00...04) contract did a shallow copy on invocation. An attacker could deploy a contract that writes X to an EVM memory region R, then calls 0x00..04 with R as an argument, then overwrites R to Y, and finally invokes the RETURNDATACOPY opcode. When this contract is invoked, a consensus-compliant node would push X on the EVM stack, whereas Geth would push Y. This is fixed in version 1.9.17.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-26241 has been found in github.com/ethereum/go-ethereum.
Data can be tampered with by attackers.
What to do: upgrade github.com/ethereum/go-ethereum to 1.9.17 or later.
If unsure, ask your IT team or search "github.com/ethereum/go-ethereum CVE-2020-26241" on the vendor's site.
CVE-2020-26241 (github.com/ethereum/go-ethereum) — CWE-682
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.9.17 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-682) exists in github.com/ethereum/go-ethereum.
Check the vendor advisory for the affected versions of github.com/ethereum/go-ethereum.
Severity: ?. Data can be tampered with by attackers.
Update to 1.9.17.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/ethereum/go-ethereum' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/ethereum/go-ethereum' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/ethereum/go-ethereumを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/ethereum/go-ethereum to 1.9.17ステージング環境で 1.9.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory blog.ethereum.org
- package github.com
- web github.com
- web blog.ethereum.org