CVE-2020-15091: Github.com/tendermint/tendermint Denial of Service Vulnerability

MODERATE
Advisory Identifier: GHSA-6jqj-f58p-mrw3
CVSS 6.5
CWE-347
Published
Advisory Summary

CVE-2020-15091 is a MODERATE (CVSS 6.5) denial of service vulnerability (CWE-347: Improper Verification of Cryptographic Signature) affecting Github.com/tendermint/tendermint libraries in the Go ecosystem. The issue involves denial of service in tendermint. Remediation is available by upgrading affected packages to version 0.33.6.

CVE-2020-15091 at a Glance

CVE Identifier CVE-2020-15091
GHSA Identifier GHSA-6jqj-f58p-mrw3
Severity MODERATE
CVSS v3.1 Base Score 6.5
CWE Classification CWE-347: Improper Verification of Cryptographic Signature
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-2020-15091

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.33.6
Upgrade github.com/tendermint/tendermint to 0.33.6
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-2020-15091, 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.33.6), 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-347: Improper Verification of Cryptographic Signature, where the product does not verify, or incorrectly verifies, the cryptographic signature for data. 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 **Denial of Service** Tendermint 0.33.0 and above allow block proposers to include signatures for the wrong block. This may happen naturally if you start a network, have it run for some time and restart it without changing the chainID. (It is a [misconfiguration](https://docs.tendermint.com/master/tendermint-core/using-tendermint.html) to reuse chainIDs.) Correct block proposers will accidentally include signatures for the wrong block if they see these signatures, and then commits won't validate, making all proposed blocks invalid. A malicious validator (even with a minimal amount of stake) can use this vulnerability to completely halt the network. Tendermint 0.33.6 checks all the signatures are for the block with +2/3 majority before creating a commit. **False Witness** Tendermint 0.33.1 and above are no longer fully verifying commit signatures during block execution - they stop after +2/3. This means proposers can propose blocks that contain valid +2/3 signatures and then the rest of the signatures can be whatever they want. They can claim that all the other validators signed just by including a CommitSig with arbitrary signature data. While this doesn't seem to impact safety of Tendermint per se, it means that Commits may contain a lot of invalid data **. _** This was already true of blocks, since they could include invalid txs filled with garbage, but in that case the application knew that they are invalid and could punish the proposer. But since applications didn't--and don't-- verify commit signatures directly (they trust Tendermint to do that), they won't be able to detect it._ This can impact incentivization logic in the application that depends on the LastCommitInfo sent in BeginBlock, which includes which validators signed. For instance, Gaia incentivizes proposers with a bonus for including more than +2/3 of the signatures. But a proposer can now claim that bonus just by including arbitrary data for the final -1/3 of validators without actually waiting for their signatures. There may be other tricks that can be played because of this. Tendermint 0.33.6 verifies all the signatures during block execution ***. _*** Please note that the light client does not check nil votes and exits as soon as 2/3+ of the signatures are checked._ ### Impact - All nodes - The network stops due to having a commit with a wrong signature. ### Patches - v0.33.6 andn v0.34.0-dev1.0.20200702134149-480b995a3172 ### Workarounds No workarounds. ### References - https://github.com/tendermint/tendermint/issues/4926 ### 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) More information can be found [here](https://tendermint.com/security/).

CVE-2020-15091 Affected Github.com/tendermint/tendermint Versions

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

References

Frequently Asked Questions

What is CVE-2020-15091?
CVE-2020-15091 is a security vulnerability in Github.com/tendermint/tendermint involving Denial of Service in TenderMint under CWE-347: Improper Verification of Cryptographic Signature.
Which Github.com/tendermint/tendermint versions are affected?
Affected versions include releases prior to 0.33.6 across affected packages: github.com/tendermint/tendermint.
What version fixes CVE-2020-15091?
Upgrading to 0.33.6 (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.33.6. Upgrade your dependency to 0.33.6 or later.
What is the CVSS score of CVE-2020-15091?
CVE-2020-15091 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-2020-15091?
CVE-2020-15091 is classified under CWE-347: Improper Verification of Cryptographic Signature (The product does not verify, or incorrectly verifies, the cryptographic signature for data.).
How can I check Go dependencies for CVE-2020-15091?
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-6jqj-f58p-mrw3",
  "modified" : "2024-05-31T17:46:56Z",
  "published" : "2021-12-20T18:17:33Z",
  "aliases" : [ "CVE-2020-15091" ],
  "summary" : "Denial of Service in TenderMint",
  "details" : "### Description\n\n**Denial of Service**\n\nTendermint 0.33.0 and above allow block proposers to include signatures for the wrong block. This may happen naturally if you start a network, have it run for some time and restart it without changing the chainID. (It is a [misconfiguration](https://docs.tendermint.com/master/tendermint-core/using-tendermint.html) to reuse chainIDs.) Correct block proposers will accidentally include signatures for the wrong block if they see these signatures, and then commits won't validate, making all proposed blocks invalid. A malicious validator (even with a minimal amount of stake) can use this vulnerability to completely halt the network.\n\nTendermint 0.33.6 checks all the signatures are for the block with +2/3 majority before creating a commit.\n\n**False Witness**\n\nTendermint 0.33.1 and above are no longer fully verifying commit signatures during block execution - they stop after +2/3. This means proposers can propose blocks that contain valid +2/3 signatures and then the rest of the signatures can be whatever they want. They can claim that all the other validators signed just by including a CommitSig with arbitrary signature data. While this doesn't seem to impact safety of Tendermint per se, it means that Commits may contain a lot of invalid data **.\n\n_** This was already true of blocks, since they could include invalid txs filled with garbage, but in that case the application knew that they are invalid and could punish the proposer. But since applications didn't--and don't-- verify commit signatures directly (they trust Tendermint to do that), they won't be able to detect it._\n\nThis can impact incentivization logic in the application that depends on the LastCommitInfo sent in BeginBlock, which includes which validators signed. For instance, Gaia incentivizes proposers with a bonus for including more than +2/3 of the signatures. But a proposer can now claim that bonus just by including arbitrary data for the final -1/3 of validators without actually waiting for their signatures. There may be other tricks that can be played because of this.\n\nTendermint 0.33.6 verifies all the signatures during block execution ***.\n\n_*** Please note that the light client does not check nil votes and exits as soon as 2/3+ of the signatures are checked._\n\n### Impact\n\n- All nodes\n- The network stops due to having a commit with a wrong signature.\n\n### Patches\n\n- v0.33.6 andn v0.34.0-dev1.0.20200702134149-480b995a3172\n\n### Workarounds\n\nNo workarounds.\n\n### References\n\n- https://github.com/tendermint/tendermint/issues/4926\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)\n\nMore information can be found [here](https://tendermint.com/security/).",
  "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"
      }, {
        "fixed" : "0.33.6"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/tendermint/tendermint/security/advisories/GHSA-6jqj-f58p-mrw3"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2020-15091"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tendermint/tendermint/issues/4926"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tendermint/tendermint/pull/5426"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tendermint/tendermint/commit/480b995a31727593f58b361af979054d17d84340"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/tendermint/tendermint"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tendermint/tendermint/blob/master/CHANGELOG.md#v0336"
  }, {
    "type" : "WEB",
    "url" : "https://pkg.go.dev/vuln/GO-2021-0090"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-347" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-05-24T20:49:56Z",
    "nvd_published_at" : null
  }
}