GHSA-p7mv-53f2-4cwj: CometBFT Vote Extensions Panic When Receiving A Pre-commit Vulnerability

HIGH
CWE-129
Published
Advisory Summary

GHSA-p7mv-53f2-4cwj is a HIGH panic when receiving a pre-commit vulnerability (CWE-129: Improper Validation of Array Index) affecting CometBFT Vote Extensions libraries in the Go ecosystem. The issue involves panic when receiving a pre-commit with an invalid data. Remediation is available by upgrading affected packages to version 0.38.15.

GHSA-p7mv-53f2-4cwj at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-p7mv-53f2-4cwj
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-129: Improper Validation of Array Index
Affected Product CometBFT Vote Extensions
Package Ecosystem Go
Published Date
Last Updated

How to Fix GHSA-p7mv-53f2-4cwj

To remediate this vulnerability, upgrade all affected CometBFT Vote Extensions dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/cometbft/cometbft fixed: 0.38.15
Upgrade github.com/cometbft/cometbft to 0.38.15
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/cometbft/cometbft

How to Check if You Are Affected

To determine whether your application is affected by GHSA-p7mv-53f2-4cwj, inspect your project dependencies for CometBFT Vote Extensions:

inspect dependencies for github.com/cometbft/cometbft

Analyze the terminal output to locate any version of CometBFT Vote Extensions in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.38.15), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-129: Improper Validation of Array Index, where the product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array. In CometBFT Vote Extensions, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Name: ASA-2024-011: Vote Extensions: Panic when receiving a Pre-commit with an invalid data Component: CometBFT Criticality: High (Considerable Impact, and Possible Likelihood per [ACMv1.2](https://github.com/interchainio/security/blob/main/resources/CLASSIFICATION_MATRIX.md)) Affected versions: `>= 0.38.x`, unreleased `v1.x` and `main` development branches Affected users: Chain Builders + Maintainers, Validators ### Impact A CometBFT node running in a network with [vote extensions][abci-spec] enabled could produce an invalid `Vote` message and send it to its peers. The invalid field of the `Vote` message is the `ValidatorIndex`, which identifies the sender in the `ValidatorSet` running that height of consensus. This field is ordinarily verified in the processing of `Vote` messages, but it turns out that in the case of a `Vote` message of type `Precommit` and for a non-`nil` `BlockID`, [a logic was introduced](https://github.com/cometbft/cometbft/blame/46621a87064b2ae235e122e66d9b22417b3aa35e/internal/consensus/state.go#L2357-L2364) before this ordinary verification to handle the attached vote extension. This introduced logic (not present in releases prior to `0.38.x`) does not double-check the validity of the `ValidatorIndex` field. The result is a panic in the execution of the node receiving and processing such message. #### Impact Qualification This condition requires the introduction of malicious code in the full node sending this `Vote` message to its peers. Namely, nodes running upstream code cannot produce invalid `Vote` messages, with non-existing `ValidatorIndex`. Moreover, networks utilizing default behavior, where vote extensions are not enabled, are not affected by this issue. ### Patches The new CometBFT release [`v0.38.15`][v0.38.15] fixes this issue. Unreleased code in the `main` and `v1.x` branches, and experimental code in the `v0.38-experimental` and `v1.x-experimental` branches are patched as well. ### Workarounds When the consensus code panics after receiving an invalid `Vote` message, the operator can identify the peer from which that message was received. This may require increasing the logging level of the `consensus` module. This peer can then be subsequently banned at the p2p layer as a temporary mitigation. ### References - [ABCI spec][abci-spec], in particular the operation of vote extensions - [Patched v0.38 release][v0.38.15] [abci-spec]: https://docs.cometbft.com/v0.38/spec/abci/abci++_basic_concepts [v0.38.15]: https://github.com/cometbft/cometbft/releases/tag/v0.38.15 ### Timeline * October 21, 2024, 3:26pm PST: Issue reported to the Cosmos Bug Bounty program * October 21, 2024, 3:41pm PST: Issue triaged by Amulet on-call, and distributed to Core team * October 29, 2024, 11:35pm PST: Core team completes validation of issue * October 30, 2024, 3:33am PST: Core team completes patch for issue * October 30, 2024, 5:09am PST: Amulet creates coordination plan; schedule for distribution * November 4, 2024, 8:00pm GMT: Pre-notification delivered * November 6, 2024, 8:00am GMT: Patch made available This issue was reported by [corverroos](https://github.com/corverroos) to the Cosmos Bug Bounty Program on HackerOne on October 21, 2024. 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 [security@interchain.io](mailto:security@interchain.io). For more information about the Interchain Foundation’s engagement with Amulet, and to sign up for security notification emails, please see https://github.com/interchainio/security. A Github Security Advisory for this issue is available in the CometBFT [repository](https://github.com/cometbft/cometbft/security/advisories/GHSA-p7mv-53f2-4cwj). For more information about CometBFT, see https://docs.cometbft.com/.

GHSA-p7mv-53f2-4cwj Affected CometBFT Vote Extensions Versions

1 component(s)
Fixed Versions:
0.38.15
Product / Package Ecosystem Affected Versions Fixed Version
github.com/cometbft/cometbft
Go
≥ 0.38.0
< 0.38.15
0.38.15

References

Frequently Asked Questions

What is GHSA-p7mv-53f2-4cwj?
GHSA-p7mv-53f2-4cwj is a security vulnerability in CometBFT Vote Extensions involving Panic when receiving a Pre-commit with an invalid data under CWE-129: Improper Validation of Array Index.
Which CometBFT Vote Extensions versions are affected?
Affected versions include releases prior to 0.38.15 across affected packages: github.com/cometbft/cometbft.
What version fixes GHSA-p7mv-53f2-4cwj?
Upgrading to 0.38.15 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/cometbft/cometbft affected?
Yes, github.com/cometbft/cometbft is affected in releases prior to 0.38.15. Upgrade your dependency to 0.38.15 or later.
What CWE is associated with GHSA-p7mv-53f2-4cwj?
GHSA-p7mv-53f2-4cwj is classified under CWE-129: Improper Validation of Array Index (The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.).
How can I check Go dependencies for GHSA-p7mv-53f2-4cwj?
Run the dependency tree command: 'inspect dependencies for github.com/cometbft/cometbft'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-p7mv-53f2-4cwj",
  "modified" : "2026-09-02T22:06:23Z",
  "published" : "2024-11-06T15:33:55Z",
  "aliases" : [ ],
  "summary" : "CometBFT Vote Extensions: Panic when receiving a Pre-commit with an invalid data",
  "details" : "Name: ASA-2024-011: Vote Extensions: Panic when receiving a Pre-commit with an invalid data\nComponent: CometBFT\nCriticality: High (Considerable Impact, and Possible Likelihood per [ACMv1.2](https://github.com/interchainio/security/blob/main/resources/CLASSIFICATION_MATRIX.md))\nAffected versions: `>= 0.38.x`, unreleased `v1.x` and `main` development branches\nAffected users: Chain Builders + Maintainers, Validators\n\n### Impact\n\nA CometBFT node running in a network with [vote extensions][abci-spec] enabled could produce an invalid `Vote` message and send it to its peers. The invalid field of the `Vote` message is the `ValidatorIndex`, which identifies the sender in the `ValidatorSet` running that height of consensus. This field is ordinarily verified in the processing of `Vote` messages, but it turns out that in the case of a `Vote` message of type `Precommit` and for a non-`nil` `BlockID`, [a logic was introduced](https://github.com/cometbft/cometbft/blame/46621a87064b2ae235e122e66d9b22417b3aa35e/internal/consensus/state.go#L2357-L2364) before this ordinary verification to handle the attached vote extension. This introduced logic (not present in releases prior to `0.38.x`) does not double-check the validity of the `ValidatorIndex` field. The result is a panic in the execution of the node receiving and processing such message.\n\n#### Impact Qualification\nThis condition requires the introduction of malicious code in the full node sending this `Vote` message to its peers. Namely, nodes running upstream code cannot produce invalid `Vote` messages, with non-existing `ValidatorIndex`. Moreover, networks utilizing default behavior, where vote extensions are not enabled, are not affected by this issue.\n\n### Patches\n\nThe new CometBFT release [`v0.38.15`][v0.38.15] fixes this issue.\n\nUnreleased code in the `main` and `v1.x` branches, and experimental code in the `v0.38-experimental` and `v1.x-experimental` branches are patched as well.\n\n### Workarounds\n\nWhen the consensus code panics after receiving an invalid `Vote` message, the operator can identify the peer from which that message was received. This may require increasing the logging level of the `consensus` module. This peer can then be subsequently banned at the p2p layer as a temporary mitigation.  \n\n### References\n\n- [ABCI spec][abci-spec], in particular the operation of vote extensions\n- [Patched v0.38 release][v0.38.15]\n\n[abci-spec]: https://docs.cometbft.com/v0.38/spec/abci/abci++_basic_concepts\n[v0.38.15]: https://github.com/cometbft/cometbft/releases/tag/v0.38.15\n\n### Timeline\n\n* October 21, 2024, 3:26pm PST: Issue reported to the Cosmos Bug Bounty program\n* October 21, 2024, 3:41pm PST: Issue triaged by Amulet on-call, and distributed to Core team\n* October 29, 2024, 11:35pm PST: Core team completes validation of issue\n* October 30, 2024, 3:33am PST: Core team completes patch for issue\n* October 30, 2024, 5:09am PST: Amulet creates coordination plan; schedule for distribution\n* November 4, 2024, 8:00pm GMT: Pre-notification delivered\n* November 6, 2024, 8:00am GMT: Patch made available\n\n\nThis issue was reported by [corverroos](https://github.com/corverroos) to the Cosmos Bug Bounty Program on HackerOne on October 21, 2024. 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.\n\nIf you have questions about Interchain security efforts, please reach out to our official communication channel at [security@interchain.io](mailto:security@interchain.io).  For more information about the Interchain Foundation’s engagement with Amulet, and to sign up for security notification emails, please see https://github.com/interchainio/security.  \n\nA Github Security Advisory for this issue is available in the CometBFT [repository](https://github.com/cometbft/cometbft/security/advisories/GHSA-p7mv-53f2-4cwj). For more information about CometBFT, see https://docs.cometbft.com/.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/cometbft/cometbft"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.38.0"
      }, {
        "fixed" : "0.38.15"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/cometbft/cometbft/security/advisories/GHSA-p7mv-53f2-4cwj"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/cometbft/cometbft/commit/17d3bb66664cab6d6798c17e27198e15bbac1905"
  }, {
    "type" : "WEB",
    "url" : "https://docs.cometbft.com/v0.38/spec/abci/abci++_basic_concepts"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/cometbft/cometbft"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/cometbft/cometbft/releases/tag/v0.38.15"
  }, {
    "type" : "WEB",
    "url" : "https://nrdax.com/techniques/NRDAX-T0211"
  }, {
    "type" : "WEB",
    "url" : "https://pkg.go.dev/vuln/GO-2024-3259"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-129" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-11-06T15:33:55Z",
    "nvd_published_at" : null
  }
}