CVE-2020-5303
Tendermint Denial-of-Service Memory Exhaustion Vulnerability
Description
Tendermint before versions 0.33.3, 0.32.10, and 0.31.12 has a denial-of-service vulnerability. Tendermint does not limit the number of P2P connection requests. For each p2p connection, it allocates XXX bytes. Even though this memory is garbage collected once the connection is terminated (due to duplicate IP or reaching a maximum number of inbound peers), temporary memory spikes can lead to OOM (Out-Of-Memory) exceptions. Additionally, Tendermint does not reclaim activeID of a peer after it's removed in Mempool reactor. This does not happen all the time. It only happens when a connection fails (for any reason) before the Peer is created and added to all reactors. RemovePeer is therefore called before AddPeer, which leads to always growing memory (activeIDs map). The activeIDs map has a maximum size of 65535 and the node will panic if this map reaches the maximum. An attacker can create a lot of connection attempts (exploiting above denial of service), which ultimately will lead to the node panicking. These issues are patched in Tendermint 0.33.3 and 0.32.10.
INFO
Published Date :
April 10, 2020, 7:15 p.m.
Last Modified :
Nov. 21, 2024, 5:33 a.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 2.0 | MEDIUM | [email protected] | ||||
| CVSS 3.1 | LOW | [email protected] | ||||
| CVSS 3.1 | LOW | [email protected] |
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2020-5303.
| URL | Resource |
|---|---|
| https://github.com/tendermint/tendermint/commit/e2d6859afd7dba4cf97c7f7d412e7d8fc908d1cd | Patch Third Party Advisory |
| https://github.com/tendermint/tendermint/security/advisories/GHSA-v24h-pjjv-mcp6 | Third Party Advisory |
| https://hackerone.com/reports/820317 | Permissions Required Third Party Advisory |
| https://github.com/tendermint/tendermint/commit/e2d6859afd7dba4cf97c7f7d412e7d8fc908d1cd | Patch Third Party Advisory |
| https://github.com/tendermint/tendermint/security/advisories/GHSA-v24h-pjjv-mcp6 | Third Party Advisory |
| https://hackerone.com/reports/820317 | Permissions Required Third Party Advisory |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2020-5303 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2020-5303
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2020-5303 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2020-5303 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://github.com/tendermint/tendermint/commit/e2d6859afd7dba4cf97c7f7d412e7d8fc908d1cd Added Reference https://github.com/tendermint/tendermint/security/advisories/GHSA-v24h-pjjv-mcp6 Added Reference https://hackerone.com/reports/820317 -
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
CVE Modified by [email protected]
Jun. 30, 2020
Action Type Old Value New Value Changed Description Tendermint before versions 0.33.3, 0.32.10, and 0.31.12 has a denial-of-service vulnerability. Tendermint does not limit the number of P2P connection requests. For each p2p connection, it allocates XXX bytes. Even though this memory is garbage collected once the connection is terminated (due to duplicate IP or reaching a maximum number of inbound peers), temporary memory spikes can lead to OOM (Out-Of-Memory) exceptions. Additionally, Tendermint does not reclaim `activeID` of a peer after it's removed in Mempool reactor. This does not happen all the time. It only happens when a connection fails (for any reason) before the Peer is created and added to all reactors. RemovePeer is therefore called before `AddPeer`, which leads to always growing memory (`activeIDs` map). The activeIDs map has a maximum size of 65535 and the node will panic if this map reaches the maximum. An attacker can create a lot of connection attempts (exploiting above denial of service), which ultimately will lead to the node panicking. These issues are patched in Tendermint 0.33.3 and 0.32.10. ### For more information If you have any questions or comments about this advisory: * Open an issue in tendermint/tendermint * Email us at [[email protected]](mailto:[email protected]) More information can be found here. ### Credits - Ethan Buchman (@ebuchman) for writing a test case for Denial of Service 2 and Tess Rinearson (@tessr) for fixing it - Anton Kaliaev (@melekes) for fixing Denial of Service 1 Tendermint before versions 0.33.3, 0.32.10, and 0.31.12 has a denial-of-service vulnerability. Tendermint does not limit the number of P2P connection requests. For each p2p connection, it allocates XXX bytes. Even though this memory is garbage collected once the connection is terminated (due to duplicate IP or reaching a maximum number of inbound peers), temporary memory spikes can lead to OOM (Out-Of-Memory) exceptions. Additionally, Tendermint does not reclaim activeID of a peer after it's removed in Mempool reactor. This does not happen all the time. It only happens when a connection fails (for any reason) before the Peer is created and added to all reactors. RemovePeer is therefore called before AddPeer, which leads to always growing memory (activeIDs map). The activeIDs map has a maximum size of 65535 and the node will panic if this map reaches the maximum. An attacker can create a lot of connection attempts (exploiting above denial of service), which ultimately will lead to the node panicking. These issues are patched in Tendermint 0.33.3 and 0.32.10. -
Initial Analysis by [email protected]
Apr. 13, 2020
Action Type Old Value New Value Added CVSS V2 NIST (AV:N/AC:M/Au:N/C:N/I:N/A:P) Added CVSS V3.1 NIST AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L Changed Reference Type https://github.com/tendermint/tendermint/commit/e2d6859afd7dba4cf97c7f7d412e7d8fc908d1cd No Types Assigned https://github.com/tendermint/tendermint/commit/e2d6859afd7dba4cf97c7f7d412e7d8fc908d1cd Patch, Third Party Advisory Changed Reference Type https://github.com/tendermint/tendermint/security/advisories/GHSA-v24h-pjjv-mcp6 No Types Assigned https://github.com/tendermint/tendermint/security/advisories/GHSA-v24h-pjjv-mcp6 Third Party Advisory Changed Reference Type https://hackerone.com/reports/820317 No Types Assigned https://hackerone.com/reports/820317 Permissions Required, Third Party Advisory Added CWE NIST CWE-787 Added CPE Configuration OR *cpe:2.3:a:tendermint:tendermint:*:*:*:*:*:*:*:* versions up to (excluding) 0.31.12 *cpe:2.3:a:tendermint:tendermint:*:*:*:*:*:*:*:* versions from (including) 0.32.0 up to (excluding) 0.32.10 *cpe:2.3:a:tendermint:tendermint:*:*:*:*:*:*:*:* versions from (including) 0.33.0 up to (excluding) 0.33.3
Vulnerability Scoring Details
Base CVSS Score: 3.7
Base CVSS Score: 4.3
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.32 }} -0.06%
score
0.51642
percentile