Uncontrolled resource consumption during consensus in github.com/tendermint/tendermint
Published 14 Oct 2022 · Updated 20 May 2024
Is your project on an affected github.com/tendermint/tendermint?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=0.34.0 <0.34.3
- Fixed in
- 0.34.3
go get github.com/tendermint/tendermint@v0.34.3Details
Mishandling of timestamps during consensus process can cause a denial of service.
While reaching consensus, different tendermint nodes can observe a different timestamp for a consensus evidence. This mismatch can cause the evidence to be invalid, upon which the node producing the evidence will be asked to generate a new evidence. This new evidence will be the same, which means it will again be rejected by other nodes involved in the consensus. This loop will continue until the peer nodes decide to disconnect from the node producing the evidence.
Is GO-2022-1052 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/tendermint/tendermint, and gives you the command that fixes it.
More advisories for github.com/tendermint/tendermint
- HighCVE-2019-25072Tendermint Client package vulnerable to Uncontrolled Resource Consumption · 28 Dec 2022
- MediumGHSA-f3w5-v9xx-rp8pSignature verification failure in Tendermint · 20 Dec 2021
- MediumCVE-2020-15091Denial of Service in TenderMint · 20 Dec 2021
- LowCVE-2020-5303Denial of service in Tendermint · 27 May 2021
- LowCVE-2019-25072Uncontrolled resource consumption in github.com/tendermint/tendermint · 14 Apr 2021
- LowCVE-2020-15091Denial of service in github.com/tendermint/tendermint · 14 Apr 2021
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.