cve.bz

CVE-2020-5303 tendermint tendermint: Out-of-bounds Write

3.7 lowEPSS 1.4%Fix available

Low (3.7) in tendermint tendermint. EPSS 1.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/tendermint/tendermint 0.31.12, 0.32.10, 0.33.3.

On this page
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.

Severity

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
1.4% (unchanged from 1.4% a week ago; 1.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 73rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-787 Out-of-bounds Write
CWE-789 Memory Allocation with Excessive Size Value
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-5303 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-5303?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-5303?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-5303 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
tendermint:tendermintbefore 0.31.12
tendermint:tendermintfrom 0.32.0 before 0.32.10
tendermint:tendermintfrom 0.33.0 before 0.33.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-v24h-pjjv-mcp6Gogithub.com/tendermint/tendermint>=0.33.0 <0.33.30.33.3
GHSA-v24h-pjjv-mcp6Gogithub.com/tendermint/tendermint<0.31.120.31.12
GHSA-v24h-pjjv-mcp6Gogithub.com/tendermint/tendermint>=0.32.0 <0.32.100.32.10

References

Check your stackJSON