CVE-2020-26265: Github.com/ethereum/go ethereum Consensus Flaw During Block Processing Vulnerability

MODERATE
Advisory Identifier: GHSA-xw37-57qp-9mm4
CVSS 5.3
CWE-682
Published
Advisory Summary

CVE-2020-26265 is a MODERATE (CVSS 5.3) consensus flaw during block processing vulnerability (CWE-682: Incorrect Calculation) affecting Github.com/ethereum/go ethereum libraries in the Go ecosystem. The issue involves consensus flaw during block processing in github.com/ethereum/go-ethereum. Remediation is available by upgrading affected packages to version 1.9.20.

CVE-2020-26265 at a Glance

CVE Identifier CVE-2020-26265
GHSA Identifier GHSA-xw37-57qp-9mm4
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-682: Incorrect Calculation
Affected Product Github.com/ethereum/go ethereum
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2020-26265

To remediate this vulnerability, upgrade all affected Github.com/ethereum/go ethereum dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/ethereum/go-ethereum fixed: 1.9.20
Upgrade github.com/ethereum/go-ethereum to 1.9.20
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/ethereum/go-ethereum

How to Check if You Are Affected

To determine whether your application is affected by CVE-2020-26265, inspect your project dependencies for Github.com/ethereum/go ethereum:

inspect dependencies for github.com/ethereum/go-ethereum

Analyze the terminal output to locate any version of Github.com/ethereum/go ethereum in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.9.20), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-682: Incorrect Calculation, where the product performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management. In Github.com/ethereum/go ethereum, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact A consensus-vulnerability in Geth could cause a chain split, where vulnerable versions refuse to accept the canonical chain. ### Description A flaw was repoted at 2020-08-11 by John Youngseok Yang (Software Platform Lab), where a particular sequence of transactions could cause a consensus failure. - Tx 1: - `sender` invokes `caller`. - `caller` invokes `0xaa`. `0xaa` has 3 wei, does a self-destruct-to-self - `caller` does a `1 wei` -call to `0xaa`, who thereby has 1 wei (the code in `0xaa` still executed, since the tx is still ongoing, but doesn't redo the selfdestruct, it takes a different path if callvalue is non-zero) - Tx 2: - `sender` does a 5-wei call to 0xaa. No exec (since no code). In geth, the result would be that `0xaa` had `6 wei`, whereas OE reported (correctly) `5` wei. Furthermore, in geth, if the second tx was not executed, the `0xaa` would be destructed, resulting in `0 wei`. Thus obviously wrong. It was determined that the root cause was this [commit](https://github.com/ethereum/go-ethereum/commit/223b950944f494a5b4e0957fd9f92c48b09037ad) from [this PR](https://github.com/ethereum/go-ethereum/pull/19953). The semantics of `createObject` was subtly changd, into returning a non-nil object (with `deleted=true`) where it previously did not if the account had been destructed. This return value caused the new object to inherit the old `balance`: ```golang func (s *StateDB) CreateAccount(addr common.Address) { newObj, prev := s.createObject(addr) if prev != nil { newObj.setBalance(prev.data.Balance) } } ``` It was determined that the minimal possible correct fix was ```diff +++ b/core/state/statedb.go @@ -589,7 +589,10 @@ func (s *StateDB) createObject(addr common.Address) (newobj, prev *stateObject) s.journal.append(resetObjectChange{prev: prev, prevdestruct: prevdestruct}) } s.setStateObject(newobj) - return newobj, prev + if prev != nil && !prev.deleted { + return newobj, prev + } + return newobj, nil ``` ### Patches See above. The fix was included in Geth `v1.9.20` "Paragade". ### Credits The bug was found by @johnyangk and reported via bounty@ethereum.org. ### For more information If you have any questions or comments about this advisory: * Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum) * Email us at [security@ethereum.org](mailto:security@ethereum.org)

CVE-2020-26265 Affected Github.com/ethereum/go ethereum Versions

1 component(s)
Fixed Versions:
1.9.20
Product / Package Ecosystem Affected Versions Fixed Version
github.com/ethereum/go-ethereum
Go
≥ 1.9.4
< 1.9.20
1.9.20

References

Frequently Asked Questions

What is CVE-2020-26265?
CVE-2020-26265 is a security vulnerability in Github.com/ethereum/go ethereum involving Consensus flaw during block processing in github.com/ethereum/go-ethereum under CWE-682: Incorrect Calculation.
Which Github.com/ethereum/go ethereum versions are affected?
Affected versions include releases prior to 1.9.20 across affected packages: github.com/ethereum/go-ethereum.
What version fixes CVE-2020-26265?
Upgrading to 1.9.20 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/ethereum/go-ethereum affected?
Yes, github.com/ethereum/go-ethereum is affected in releases prior to 1.9.20. Upgrade your dependency to 1.9.20 or later.
What is the CVSS score of CVE-2020-26265?
CVE-2020-26265 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N.
What CWE is associated with CVE-2020-26265?
CVE-2020-26265 is classified under CWE-682: Incorrect Calculation (The product performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management.).
How can I check Go dependencies for CVE-2020-26265?
Run the dependency tree command: 'inspect dependencies for github.com/ethereum/go-ethereum'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xw37-57qp-9mm4",
  "modified" : "2023-02-09T19:40:33Z",
  "published" : "2021-06-29T21:14:16Z",
  "aliases" : [ "CVE-2020-26265" ],
  "summary" : "Consensus flaw during block processing in github.com/ethereum/go-ethereum",
  "details" : "### Impact\n\nA consensus-vulnerability in Geth could cause a chain split, where vulnerable versions refuse to accept the canonical chain. \n\n### Description\n\n\nA flaw was repoted at 2020-08-11 by John Youngseok Yang (Software Platform Lab), where a particular sequence of transactions could cause a consensus failure.\n\n- Tx 1:\n  - `sender` invokes `caller`.\n  - `caller` invokes `0xaa`. `0xaa` has 3 wei, does a self-destruct-to-self\n  - `caller` does a  `1 wei` -call to `0xaa`, who thereby has 1 wei (the code in `0xaa` still executed, since the tx is still ongoing, but doesn't redo the selfdestruct, it takes a different path if callvalue is non-zero)\n\n- Tx 2:\n  - `sender` does a 5-wei call to 0xaa. No exec (since no code). \n\nIn geth, the result would be that `0xaa` had `6 wei`, whereas OE reported (correctly) `5` wei. Furthermore, in geth, if the second tx was not executed, the `0xaa` would be destructed, resulting in `0 wei`. Thus obviously wrong. \n\nIt was determined that the root cause was this [commit](https://github.com/ethereum/go-ethereum/commit/223b950944f494a5b4e0957fd9f92c48b09037ad) from [this PR](https://github.com/ethereum/go-ethereum/pull/19953). The semantics of `createObject` was subtly changd, into returning a non-nil object (with `deleted=true`) where it previously did not if the account had been destructed. This return value caused the new object to inherit the old `balance`:\n\n```golang\nfunc (s *StateDB) CreateAccount(addr common.Address) {\n\tnewObj, prev := s.createObject(addr)\n\tif prev != nil {\n\t\tnewObj.setBalance(prev.data.Balance)\n\t}\n}\n```\n\nIt was determined that the minimal possible correct fix was\n\n```diff\n+++ b/core/state/statedb.go\n@@ -589,7 +589,10 @@ func (s *StateDB) createObject(addr common.Address) (newobj, prev *stateObject)\n                s.journal.append(resetObjectChange{prev: prev, prevdestruct: prevdestruct})\n        }\n        s.setStateObject(newobj)\n-       return newobj, prev\n+       if prev != nil && !prev.deleted {\n+               return newobj, prev\n+       }\n+       return newobj, nil\n```\n\n### Patches\n\nSee above. The fix was included in Geth `v1.9.20` \"Paragade\".\n\n### Credits\n\nThe bug was found by @johnyangk and reported via bounty@ethereum.org.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [go-ethereum](https://github.com/ethereum/go-ethereum)\n* Email us at [security@ethereum.org](mailto:security@ethereum.org)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/ethereum/go-ethereum"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.9.4"
      }, {
        "fixed" : "1.9.20"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/ethereum/go-ethereum/security/advisories/GHSA-xw37-57qp-9mm4"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2020-26265"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ethereum/go-ethereum/pull/21080"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ethereum/go-ethereum/pull/21409"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ethereum/go-ethereum/commit/87c0ba92136a75db0ab2aba1046d4a9860375d6a"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/ethereum/go-ethereum"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ethereum/go-ethereum/releases/tag/v1.9.20"
  }, {
    "type" : "WEB",
    "url" : "https://pkg.go.dev/vuln/GO-2021-0105"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-682" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-05-21T21:15:07Z",
    "nvd_published_at" : null
  }
}