GHSA-f3w5-v9xx-rp8p: Github.com/tendermint/tendermint Signature Verification Failure Vulnerability

MODERATE
CWE-347
Published
Advisory Summary

GHSA-f3w5-v9xx-rp8p is a MODERATE signature verification failure vulnerability (CWE-347: Improper Verification of Cryptographic Signature) affecting Github.com/tendermint/tendermint libraries in the Go ecosystem. The issue involves signature verification failure in tendermint. Remediation is available by upgrading affected packages to version 0.34.9.

GHSA-f3w5-v9xx-rp8p at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-f3w5-v9xx-rp8p
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-347: Improper Verification of Cryptographic Signature
Affected Product Github.com/tendermint/tendermint
Package Ecosystem Go
Published Date
Last Updated

How to Fix GHSA-f3w5-v9xx-rp8p

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.9
Upgrade github.com/tendermint/tendermint to 0.34.9
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 GHSA-f3w5-v9xx-rp8p, 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.9), 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

_The root cause of this security vulnerability is in the Tendermint specification, and this advisory is a duplicate of https://github.com/tendermint/spec/security/advisories/GHSA-jqfc-687g-59pw._ ### Impact Tendermint light clients running versions 0.34.0 to 0.34.8 are unable to detect and punish a new kind of attack. We’re calling this a “forward lunatic attack,” or FLA. The severity of this vulnerability is _moderate_. Note that an FLA cannot be successfully executed unless there are already ⅓+ Byzantine validators, and therefore outside of Tendermint’s security model; however, it is important to be able to detect and punish these kinds of attacks in order to incentivize correct behavior. In an FLA, an attacking validator (with ⅓+ voting power) signs commit messages for arbitrary application state associated with a block height that hasn’t been seen yet, hence the name “forward lunatic attacks.” A malicious validator effectively executes a [lunatic attack](https://docs.tendermint.com/master/spec/light-client/accountability/#the-misbehavior-of-faulty-validators), but signs messages for a target block that is higher than the current block. This can be dangerous: Typically, misbehavior evidence is only created when there are conflicting blocks at the same height, but by targeting a block height that is far “ahead” of the current chain height, it’s possible that the chain will not produce a (conflicting) block at the target height in time to create evidence. Prior to Tendermint v0.34.9, the light client could accept a bad header from its primary witness, and would not be able to form evidence of this deception, even if all the secondary witnesses were correct. Because the light client is responsible for verifying cross-chain state for IBC, a successful FLA could result in loss of funds. However, it is important to note that FLAs are only possible outside the Tendermint security model. All FLAs, attempted and successful, leave traces of provable misbehavior on-chain. A faulty header contains signatures from the faulty validator, and even in unpatched versions of Tendermint Core, networks could use social consensus (off-chain action) to recover the network. The patches introduced in Tendermint Core v0.34.9 handle all evidence automatically and on-chain. Note that this fix also allows for successful automatic reporting of FLAs, even after a chain halt. By adding a time to FetchBlock, light clients effectively have a backup way to determine if a halted chain should have continued, and it will be able to submit evidence as soon as the chain resumes. ### Patches This problem has been patched in Tendermint Core v0.34.9. ### Workarounds There are no workarounds. All users are recommended to upgrade to Tendermint Core v0.34.9 at their earliest possible convenience. ### Credits Thank you to @MaximilianDiez for originally surfacing this issue, and to @cmwaters, @josef-widder, and @milosevic for creating fixes at both the implementation and specification level. ### 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)

GHSA-f3w5-v9xx-rp8p Affected Github.com/tendermint/tendermint Versions

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

References

Frequently Asked Questions

What is GHSA-f3w5-v9xx-rp8p?
GHSA-f3w5-v9xx-rp8p is a security vulnerability in Github.com/tendermint/tendermint involving Signature verification failure 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.34.9 across affected packages: github.com/tendermint/tendermint.
What version fixes GHSA-f3w5-v9xx-rp8p?
Upgrading to 0.34.9 (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.9. Upgrade your dependency to 0.34.9 or later.
What CWE is associated with GHSA-f3w5-v9xx-rp8p?
GHSA-f3w5-v9xx-rp8p 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 GHSA-f3w5-v9xx-rp8p?
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-f3w5-v9xx-rp8p",
  "modified" : "2021-05-20T20:10:47Z",
  "published" : "2021-12-20T18:17:41Z",
  "aliases" : [ ],
  "summary" : "Signature verification failure in Tendermint",
  "details" : "_The root cause of this security vulnerability is in the Tendermint specification, and this advisory is a duplicate of https://github.com/tendermint/spec/security/advisories/GHSA-jqfc-687g-59pw._\n\n\n### Impact\nTendermint light clients running versions 0.34.0 to 0.34.8 are unable to detect and punish a new kind of attack. We’re calling this a “forward lunatic attack,” or FLA. The severity of this vulnerability is _moderate_. \n\nNote that an FLA cannot be successfully executed unless there are already ⅓+ Byzantine validators, and therefore outside of Tendermint’s security model; however, it is important to be able to detect and punish these kinds of attacks in order to incentivize correct behavior.\n\nIn an FLA, an attacking validator (with ⅓+ voting power) signs commit messages for arbitrary application state associated with a block height that hasn’t been seen yet, hence the name “forward lunatic attacks.” A malicious validator effectively executes a [lunatic attack](https://docs.tendermint.com/master/spec/light-client/accountability/#the-misbehavior-of-faulty-validators), but signs messages for a target block that is higher than the current block. This can be dangerous: Typically, misbehavior evidence is only created when there are conflicting blocks at the same height, but by targeting a block height that is far “ahead” of the current chain height, it’s possible that the chain will not produce a (conflicting) block at the target height in time to create evidence. \n\nPrior to Tendermint v0.34.9, the light client could accept a bad header from its primary witness, and would not be able to form evidence of this deception, even if all the secondary witnesses were correct. Because the light client is responsible for verifying cross-chain state for IBC, a successful FLA could result in loss of funds. However, it is important to note that FLAs are only possible outside the Tendermint security model. \n\nAll FLAs, attempted and successful, leave traces of provable misbehavior on-chain. A faulty header contains signatures from the faulty validator, and even in unpatched versions of Tendermint Core, networks could use social consensus (off-chain action) to recover the network. The patches introduced in Tendermint Core v0.34.9 handle all evidence automatically and on-chain. \n\nNote that this fix also allows for successful automatic reporting of FLAs, even after a chain halt. By adding a time to FetchBlock, light clients effectively have a backup way to determine if a halted chain should have continued, and it will be able to submit evidence as soon as the chain resumes. \n\n### Patches\nThis problem has been patched in Tendermint Core v0.34.9. \n\n### Workarounds\nThere are no workarounds. All users are recommended to upgrade to Tendermint Core v0.34.9 at their earliest possible convenience. \n\n### Credits\n\nThank you to @MaximilianDiez for originally surfacing this issue, and to @cmwaters, @josef-widder, and @milosevic for creating fixes at both the implementation and specification level.\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" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/tendermint/tendermint"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.34.0"
      }, {
        "fixed" : "0.34.9"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/tendermint/tendermint/security/advisories/GHSA-f3w5-v9xx-rp8p"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-347" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-05-20T20:10:47Z",
    "nvd_published_at" : null
  }
}