Read the docs
TI-2021-04371 Aliases CVE-2021-21271GHSA-p658-8693-mhvg

Denial of service in TenderMint Core

Priority LOW 32CWE-400Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-400.

Summary

Tendermint Core is an open source Byzantine Fault Tolerant (BFT) middleware that takes a state transition machine - written in any programming language - and securely replicates it on many machines. 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. 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 Votes 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.

Why it matters now

EPSS 0.01763 78th percentileScored 2026-11-07
Fix Fixed tendermint (tendermint): 0.34.3github.com/tendermint/tendermint (Go): 0.34.3

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
tenderminttendermint0.34.0 to before 0.34.30.34.3Patch availableCNA
—github.com/tendermint/tendermint (Go)0.34.0 to before 0.34.30.34.3Patch availableGHSA-p658-8693-mhvg
  • tendermint Vendortendermint Affected 0.34.0 to before 0.34.3 Fixed in 0.34.3 Patch available CNA
  • github.com/tendermint/tendermint (Go) Vendor— Affected 0.34.0 to before 0.34.3 Fixed in 0.34.3 Patch available GHSA-p658-8693-mhvg

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:tendermint:tendermint:*:*:*:*:*:*:*:*0.34.0 – 0.34.2Vulnerabletendermint
  • cpe:2.3:a:tendermint:tendermint:*:*:*:*:*:*:*:* Versions 0.34.0 – 0.34.2 Vulnerable ·tendermint

Remediation

  • Fix · CNA tendermint (tendermint) Fixed in 0.34.3
  • Fix · GHSA-p658-8693-mhvg github.com/tendermint/tendermint (Go) Fixed in 0.34.3 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2021-21271
  2. 2026-10-03 Alias added: GHSA-p658-8693-mhvg

References

  • TI-2019-15212 Uncontrolled resource consumption in github.com/tendermint/tendermint CVSS 3.1HIGH 7.5
  • TI-2020-11866 Denial of Service in TenderMint CVSS 3.1MEDIUM 6.5
  • TI-2020-04359 Denial of service in Tendermint CVSS 3.1LOW 3.7

Sources