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.
References
Link | Resource |
---|---|
https://github.com/tendermint/tendermint/commit/480b995a31727593f58b361af979054d17d84340 | Patch Third Party Advisory |
https://github.com/tendermint/tendermint/issues/4926 | Exploit Issue Tracking Third Party Advisory |
https://github.com/tendermint/tendermint/security/advisories/GHSA-6jqj-f58p-mrw3 | Exploit Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: GitHub_M
Published: 2020-07-02T17:05:15
Updated: 2020-07-02T17:05:15
Reserved: 2020-06-25T00:00:00
Link: CVE-2020-15091
JSON object: View
NVD Information
Status : Analyzed
Published: 2020-07-02T17:15:12.547
Modified: 2020-07-08T19:16:14.410
Link: CVE-2020-15091
JSON object: View
Redhat Information
No data.
CWE