Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2020-5303

Out-of-Bounds Write in github.com/tendermint/tendermint (CVE-2020-5303)

Summary

Out-of-bounds write in github.com/tendermint/tendermint (CVE-2020-5303). Risk of unauthorized operations or information disclosure. Exploitable via activeID. Mitigation: upgrade to 0.32.10 or later.

Original description

The description as published by the source.

Description

Denial of Service 1

Tendermint 0.33.2 and earlier does not limit the number of P2P connection requests. For each p2p connection, Tendermint 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.

Tendermint 0.33.3 (and 0.32.10) limits the total number of P2P incoming connection requests to to p2p.max_num_inbound_peers + len(p2p.unconditional_peer_ids).

Notes:

Denial of Service 2

Tendermint 0.33.2 and earlier 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 o…

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-5303 has been found in github.com/tendermint/tendermint.
Attackers can target a specific entry point like activeID over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/tendermint/tendermint to 0.32.10 or later.
If unsure, ask your IT team or search "github.com/tendermint/tendermint CVE-2020-5303" on the vendor's site.

CVE-2020-5303 (github.com/tendermint/tendermint) — CWE-787
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: activeID / Mempool / Peer / RemovePeer
Patched: 0.32.10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Out-of-bounds write (CWE-787) exists in github.com/tendermint/tendermint. Attackers reach the vulnerable code path via activeID without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/tendermint/tendermint. Attack surface: activeID / Mempool / Peer / RemovePeer.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.32.10.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/tendermint/tendermint' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/tendermint/tendermint' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/tendermint/tendermint を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/tendermint/tendermint to 0.32.10

    ステージング環境で 0.32.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go github.com/tendermint/tendermint
[{"type":"SEMVER","events":[{"introduced":"0.32.0"},{"fixed":"0.32.10"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details