Summary
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
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].
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.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
github.com/cometbft/cometbft to 0.37.7 or later; github.com/cometbft/cometbft to 0.38.8 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-HG58-RF2H-6RR7? GHSA-HG58-RF2H-6RR7 is a medium-severity security vulnerability in github.com/cometbft/cometbft (go), affecting versions >= 0.37.0, < 0.37.7. It is fixed in 0.37.7, 0.38.8.
- Which versions of github.com/cometbft/cometbft are affected by GHSA-HG58-RF2H-6RR7? github.com/cometbft/cometbft (go) versions >= 0.37.0, < 0.37.7 is affected.
- Is there a fix for GHSA-HG58-RF2H-6RR7? Yes. GHSA-HG58-RF2H-6RR7 is fixed in 0.37.7, 0.38.8. Upgrade to this version or later.
- Is GHSA-HG58-RF2H-6RR7 exploitable, and should I be worried? Whether GHSA-HG58-RF2H-6RR7 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-HG58-RF2H-6RR7 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-HG58-RF2H-6RR7?
- Upgrade
github.com/cometbft/cometbftto 0.37.7 or later - Upgrade
github.com/cometbft/cometbftto 0.38.8 or later
- Upgrade