Detections
Analytics

SCA: security update for github.com/tendermint/tendermint (GHSA-p658-8693-mhvg)

medium Tenable Cloud Security Plugin ID 433659

Description

There are packages installed that are affected by a vulnerability referenced in the following CVE:

 - 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.
 (CVE-2021-21271)

See Also

https://github.com/advisories/GHSA-p658-8693-mhvg

Plugin Details

Severity: Medium

ID: 433659

Version: Revision 1.3

Type: Local

Family: SCA Checks

Published: 8/19/2025

Updated: 7/2/2026

Supported Sensors: Tenable Cloud Security, Tenable Self-Hosted Container Security

Risk Information

VPR

Risk Factor: Low

Score: 3

Percentile: 23.18

Vendor

Vendor Severity: Medium

CVSS v2

Risk Factor: Medium

Base Score: 4

Temporal Score: 3

Vector: CVSS2#AV:N/AC:L/Au:S/C:N/I:N/A:P

CVSS Score Source: CVE-2021-21271

CVSS v3

Risk Factor: Medium

Base Score: 6.5

Temporal Score: 5.7

Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Temporal Vector: CVSS:3.0/E:U/RL:O/RC:C

Vulnerability Information

Exploit Ease: No known exploits are available

Patch Publication Date: 10/7/2022

Vulnerability Publication Date: 1/26/2021

Reference Information

CVE: CVE-2021-21271

cwe: CWE-400