CVE-2021-21271: Github.com/tendermint/tendermint Remote Code Execution Vulnerability

MODERATE
Advisory Identifier: GHSA-p658-8693-mhvg
CVSS 6.5
CWE-400
Published
Advisory Summary

CVE-2021-21271 is a MODERATE (CVSS 6.5) remote code execution vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting Github.com/tendermint/tendermint libraries in the Go ecosystem. The issue involves tendermint core vulnerable to uncontrolled resource consumption. Remediation is available by upgrading affected packages to version 0.34.3.

CVE-2021-21271 at a Glance

CVE Identifier CVE-2021-21271
GHSA Identifier GHSA-p658-8693-mhvg
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-400: Uncontrolled Resource Consumption
Affected Product Github.com/tendermint/tendermint
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 6.5

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

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

How to Fix CVE-2021-21271

To remediate this vulnerability, upgrade all affected Github.com/tendermint/tendermint 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/tendermint/tendermint fixed: 0.34.3
Upgrade github.com/tendermint/tendermint to 0.34.3
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/tendermint/tendermint

How to Check if You Are Affected

To determine whether your application is affected by CVE-2021-21271, inspect your project dependencies for Github.com/tendermint/tendermint:

inspect dependencies for github.com/tendermint/tendermint

Analyze the terminal output to locate any version of Github.com/tendermint/tendermint in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.34.3), 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-400: Uncontrolled Resource Consumption, where the product does not properly control the allocation and maintenance of a limited resource. In Github.com/tendermint/tendermint, 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

### Description Tendermint Core v0.34.0 introduced a new way of handling evidence of misbehavior. As part of this, [we added a new `Timestamp` field to `Evidence` structs](https://github.com/tendermint/tendermint/pull/5219). This timestamp would be calculated using the same algorithm that is used when a block is created and proposed. (This algorithm relies on the timestamp of the last commit from this specific block.) In Tendermint Core v0.34.0-v0.34.2, the `consensus` reactor is responsible for forming `DuplicateVoteEvidence` whenever double signs are observed. However, the current block is still “in flight” when it is being formed by the `consensus` reactor. It hasn’t been finalized through network consensus yet. This means that different nodes in the network may observe different “last commits” when assigning a timestamp to `DuplicateVoteEvidence.` In turn, different nodes could form `DuplicateVoteEvidence` objects at the same height but with different timestamps. One `DuplicateVoteEvidence` object (with one timestamp) will then eventually get finalized in the block, but this means that any `DuplicateVoteEvidence` with a different timestamp is considered invalid. Any node that formed invalid `DuplicateVoteEvidence` will continue to propose invalid evidence; its peers may see this, and choose to disconnect from this node. This bug means that double signs are DoS vectors in Tendermint Core v0.34.0-v0.34.2. Tendermint Core v0.34.3 is a security release which fixes this bug. As of v0.34.3, `DuplicateVoteEvidence` is no longer formed by the `consensus` reactor; rather, the `consensus` reactor passes the `Vote`s themselves into the `EvidencePool`, which is now responsible for forming `DuplicateVoteEvidence`. The `EvidencePool` has timestamp info that should be consistent across the network, which means that `DuplicateVoteEvidence` formed in this reactor should have consistent timestamps. This release changes the API between the `consensus` and `evidence` reactors. ### Impact This is a denial-of-service vector which impacts networks running Tendermint Core v0.34.0 - v0.34.2. ### Remediation This problem has been patched in Tendermint Core v0.34.3. Networks running impacted versions of Tendermint Core should update immediately. ### Workarounds There are no workarounds, other than upgrading to a patched version of Tendermint Core. ### Credits * Crypto.com (@cyril-crypto, @brianatcrypto, @tomtau and @yihuang) for finding and submitting this vulnerability * @melekes and @cmwaters for identifying the root cause and patching the problem ### For more information If you have any questions or comments about this advisory: * Open an issue in [tendermint/tendermint](https://github.com/tendermint/tendermint) * Email us at [security@tendermint.com](mailto:security@tendermint.com)

CVE-2021-21271 Affected Github.com/tendermint/tendermint Versions

1 component(s)
Fixed Versions:
0.34.3
Product / Package Ecosystem Affected Versions Fixed Version
github.com/tendermint/tendermint
Go
≥ 0.34.0
< 0.34.3
0.34.3

References

Frequently Asked Questions

What is CVE-2021-21271?
CVE-2021-21271 is a security vulnerability in Github.com/tendermint/tendermint involving Tendermint Core vulnerable to Uncontrolled Resource Consumption under CWE-400: Uncontrolled Resource Consumption.
Which Github.com/tendermint/tendermint versions are affected?
Affected versions include releases prior to 0.34.3 across affected packages: github.com/tendermint/tendermint.
What version fixes CVE-2021-21271?
Upgrading to 0.34.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/tendermint/tendermint affected?
Yes, github.com/tendermint/tendermint is affected in releases prior to 0.34.3. Upgrade your dependency to 0.34.3 or later.
What is the CVSS score of CVE-2021-21271?
CVE-2021-21271 has a CVSS v3.1 base score of 6.5 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2021-21271?
CVE-2021-21271 is classified under CWE-400: Uncontrolled Resource Consumption (The product does not properly control the allocation and maintenance of a limited resource.).
How can I check Go dependencies for CVE-2021-21271?
Run the dependency tree command: 'inspect dependencies for github.com/tendermint/tendermint'. 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-p658-8693-mhvg",
  "modified" : "2024-05-31T16:54:40Z",
  "published" : "2022-10-07T07:23:51Z",
  "aliases" : [ "CVE-2021-21271" ],
  "summary" : "Tendermint Core vulnerable to Uncontrolled Resource Consumption",
  "details" : "### Description \n\nTendermint Core v0.34.0 introduced a new way of handling evidence of misbehavior. As part of this, [we added a new `Timestamp` field to `Evidence` structs](https://github.com/tendermint/tendermint/pull/5219). This timestamp would be calculated using the same algorithm that is used when a block is created and proposed. (This algorithm relies on the timestamp of the last commit from this specific block.) \n\nIn Tendermint Core v0.34.0-v0.34.2, the `consensus` reactor is responsible for forming `DuplicateVoteEvidence` whenever double signs are observed. However, the current block is still “in flight” when it is being formed by the `consensus` reactor. It hasn’t been finalized through network consensus yet. This means that different nodes in the network may observe different “last commits” when assigning a timestamp to `DuplicateVoteEvidence.`\n\nIn turn, different nodes could form `DuplicateVoteEvidence` objects at the same height but with different timestamps. One `DuplicateVoteEvidence` object (with one timestamp) will then eventually get finalized in the block, but this means that any `DuplicateVoteEvidence` with a different timestamp is considered invalid. Any node that formed invalid `DuplicateVoteEvidence` will continue to propose invalid evidence; its peers may see this, and choose to disconnect from this node. This bug means that double signs are DoS vectors in Tendermint Core v0.34.0-v0.34.2. \n\nTendermint Core v0.34.3 is a security release which fixes this bug. As of v0.34.3, `DuplicateVoteEvidence` is no longer formed by the `consensus` reactor; rather, the `consensus` reactor passes the `Vote`s themselves into the `EvidencePool`, which is now responsible for forming `DuplicateVoteEvidence`. The `EvidencePool` has timestamp info that should be consistent across the network, which means that `DuplicateVoteEvidence` formed in this reactor should have consistent timestamps. \n\nThis release changes the API between the `consensus` and `evidence` reactors. \n\n### Impact\n\nThis is a denial-of-service vector which impacts networks running Tendermint Core v0.34.0 - v0.34.2.\n\n### Remediation\n\nThis problem has been patched in Tendermint Core v0.34.3. Networks running impacted versions of Tendermint Core should update immediately.\n\n### Workarounds\n\nThere are no workarounds, other than upgrading to a patched version of Tendermint Core.\n\n### Credits \n\n* Crypto.com (@cyril-crypto, @brianatcrypto, @tomtau and  @yihuang) for finding and submitting this vulnerability\n* @melekes and @cmwaters for identifying the root cause and patching the problem \n\n### For more information\n\nIf you have any questions or comments about this advisory:\n* Open an issue in [tendermint/tendermint](https://github.com/tendermint/tendermint)\n* Email us at [security@tendermint.com](mailto:security@tendermint.com)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/tendermint/tendermint"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.34.0"
      }, {
        "fixed" : "0.34.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/tendermint/tendermint/security/advisories/GHSA-p658-8693-mhvg"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2021-21271"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tendermint/tendermint/pull/5219"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tendermint/tendermint/commit/a2a6852ab99e4a0f9e79f0ea8c1726e262e25c76"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/tendermint/tendermint"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tendermint/tendermint/blob/v0.34.3/CHANGELOG.md#v0.34.3"
  }, {
    "type" : "WEB",
    "url" : "https://pkg.go.dev/vuln/GO-2022-1052"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-400" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-10-07T07:23:51Z",
    "nvd_published_at" : null
  }
}