TenderMint from version 0.33.0 and before version 0.33.6 allows 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 chainID). A malicious block proposer (even with a minimal amount of stake) can use this vulnerability to completely halt the network. This issue is fixed in Tendermint 0.33.6 which checks all the signatures are for the block with 2/3+ majority before creating a commit.
Weakness
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Tendermint | Tendermint | 0.33.0 (including) | 0.33.6 (excluding) |
Related Attack Patterns
References
- https://github.com/tendermint/tendermint/commit/480b995a31727593f58b361af979054d17d84340
- https://github.com/tendermint/tendermint/issues/4926
- https://github.com/tendermint/tendermint/security/advisories/GHSA-6jqj-f58p-mrw3
- https://github.com/tendermint/tendermint/commit/480b995a31727593f58b361af979054d17d84340
- https://github.com/tendermint/tendermint/issues/4926
- https://github.com/tendermint/tendermint/security/advisories/GHSA-6jqj-f58p-mrw3