CVE-2021-21271: Uncontrolled resource consumption during consensus in github.com/tendermint/tendermint

Summary

14/10/2022
Yes i
Moderate
6.5

CVE-2021-21271: Uncontrolled resource consumption during consensus in github.com/tendermint/tendermint. Affects github.com/tendermint/tendermint versions >= 0.34.0, < 0.34.3. Fixed in 0.34.3. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package under scrutiny is github.com/tendermint/tendermint, which is written in Go. Tendermint is a Byzantine Fault Tolerant (BFT) consensus engine that enables secure and consistent replication of an application on multiple machines. It is commonly used as the consensus layer in blockchain systems. The vulnerability affects versions 0.34.0 to 0.34.2 of the package.

Vulnerability Detail

The vulnerability arises from the mishandling of timestamps during the consensus process in Tendermint. When different Tendermint nodes observe a different timestamp for a consensus evidence, it can lead to a mismatch and render the evidence invalid. As a result, the node producing the evidence will be requested to generate a new evidence. However, this new evidence will be identical to the previous one, causing it to be rejected again by other nodes involved in the consensus. This loop continues until the peer nodes decide to disconnect from the node producing the evidence. This vulnerability can be exploited to launch a denial of service attack, causing uncontrolled resource consumption and potentially disrupting the consensus process.

How To Fix

Minimum fixed version

0.34.3

This is the first release that contains the fix.

go get github.com/tendermint/tendermint@v0.34.3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to upgrade to the fixed version of the package to mitigate the risk.

Conclusion

The vulnerability in github.com/tendermint/tendermint can lead to uncontrolled resource consumption during the consensus process, potentially causing a denial of service. To mitigate this risk, it is crucial to upgrade to version 0.34.3 or later of the package. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for github.com/tendermint/tendermint →

Share this vulnerability

FAQ

Tendermint is a Byzantine Fault Tolerant (BFT) consensus engine used for secure and consistent replication of applications on multiple machines. It is commonly used as the consensus layer in blockchain systems.

This vulnerability can be exploited to launch a denial of service attack, causing uncontrolled resource consumption and potentially disrupting the consensus process in Tendermint-based systems.

Versions 0.34.0 to 0.34.2 of github.com/tendermint/tendermint are affected by this vulnerability.

No, there is no known workaround for this vulnerability. It is crucial to upgrade to the fixed version of the package.

To fix this vulnerability, it is recommended to upgrade to version 0.34.3 or later of github.com/tendermint/tendermint.

Related vulnerabilities

Recent vulnerabilities recorded for github.com/tendermint/tendermint.

How To Fix

Minimum fixed version

0.34.3

This is the first release that contains the fix.

go get github.com/tendermint/tendermint@v0.34.3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback