Denial of service when syncing with a malicious peer in github.com/cometbft/cometbft
Published 2 Jul 2024 · Updated 2 Jul 2024
Is your project on an affected github.com/cometbft/cometbft?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=0.37.0 <0.37.7 · >=0.38.0 <0.38.8
- Fixed in
- 0.37.7, 0.38.8
go get github.com/cometbft/cometbft@v0.38.8Details
A malicious peer can cause a syncing node to panic during blocksync. The syncing node may enter into a catastrophic invalid syncing state or get stuck in blocksync mode, never switching to consensus. Nodes that are vulnerable to this state may experience a Denial of Service condition in which syncing will not work as expected when joining a network as a client.
Is GO-2024-2951 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/cometbft/cometbft, and gives you the command that fixes it.
More advisories for github.com/cometbft/cometbft
- LowGO-2026-4361Inconsistencies between how commit signatures are verified and how block time is derived in github.com/cometbft/cometbft · 19 Feb 2026
- HighGHSA-c32p-wcqj-j677CometBFT has inconsistencies between how commit signatures are verified and how block time is derived · 23 Jan 2026
- LowGO-2025-4025CometBFT's invalid BitArray handling can lead to network halt in github.com/cometbft/cometbft · 18 Nov 2025
- HighGHSA-hrhf-2vcr-ghchCometBFT's invalid BitArray handling can lead to network halt · 14 Oct 2025
- LowCVE-2025-24371CometBFT allows a malicious peer to make node stuck in blocksync in github.com/cometbft/cometbft · 4 Feb 2025
- LowGO-2025-3443CometBFT allows a malicious peer to stall network by disseminating valid-looking block parts in github.com/cometbft/cometbft · 4 Feb 2025
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.