GHSA-hg58-rf2h-6rr7: CometBFT is unstability during blocksync when syncing from malicious peer
Name: ASA-2024-008: Instability during blocksync when syncing from malicious peer Component: CometBFT Criticality: Medium (ACMv1: I:Moderate; L: Possible) Affected versions: < v0.38.7 Summary An issue was identified for nodes syncing on an existing network during blocksync in which a malicious peer could cause the syncing peer to panic, enter into a catastrophic invalid syncing state or get stuck in blocksync mode,…
Published Jun 28, 2024 · Updated Jul 5, 2024
Affected packages
github.com/cometbft/cometbft
- Ecosystem
- Go
- Affected
- >= 0.37.0, < 0.37.7
- Fixed in
- 0.37.7
- Check
go list -m github.com/cometbft/cometbft
github.com/cometbft/cometbft
- Ecosystem
- Go
- Affected
- >= 0.38.0, < 0.38.8
- Fixed in
- 0.38.8
- Check
go list -m github.com/cometbft/cometbft
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Name: ASA-2024-008: Instability during blocksync when syncing from malicious peer Component: CometBFT Criticality: Medium (ACMv1: I:Moderate; L: Possible) Affected versions: < v0.38.7
Summary
An issue was identified for nodes syncing on an existing network during blocksync in which a malicious peer could cause the syncing peer to panic, enter into a catastrophic invalid syncing state or get stuck in blocksync mode, never switching to consensus. It is recommended for all clients to adopt this patch so that blocksync functions as expected and is tolerant of malicious peers presenting invalid data in this situation. 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.
Recognition
This issue was reported to the Cosmos Bug Bounty Program on HackerOne on 5/01/24 by unknown_feature. If you believe you have found a bug in the Interchain Stack or would like to contribute to the program by reporting a bug, please see https://hackerone.com/cosmos.
If you have questions about Interchain security efforts, please reach out to our official communication channel at [[email protected]](mailto:[email protected]).
For more information about CometBFT, please see https://docs.cometbft.com/.
For more information about the Interchain Foundation’s engagement with Amulet, please see https://github.com/interchainio/security.
Credited to unknownfeature.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesGHSA-c32p-wcqj-j677
CometBFT has inconsistencies between how commit signatures are verified and how block time is derived
high7.1Jan 23, 2026GHSA-hrhf-2vcr-ghch
CometBFT's invalid BitArray handling can lead to network halt
high8.7Oct 14, 2025CVE-2025-24371
CometBFT allows a malicious peer to make node stuck in blocksync
medium6.9Feb 3, 2025GHSA-r3r4-g7hq-pq4f
CometBFT allows a malicious peer to stall the network by disseminating seemingly valid block parts
highFeb 3, 2025GHSA-p7mv-53f2-4cwj
CometBFT Vote Extensions: Panic when receiving a Pre-commit with an invalid data
high8.3Nov 6, 2024GHSA-g5xx-c4hv-9ccc
CometBFT's state syncing validator from malicious node may lead to a chain split
low4.7Sep 3, 2024
