CVE-2023-34451: Github.com/cometbft/cometbft CometBFT May Duplicate Transactions Vulnerability

HIGH
Advisory Identifier: GHSA-w24w-wp77-qffm
CVSS 8.2
CWE-401
Published
Advisory Summary

CVE-2023-34451 is a HIGH (CVSS 8.2) cometbft may duplicate transactions vulnerability (CWE-401: Missing Release of Memory after Effective Lifetime) affecting Github.com/cometbft/cometbft libraries in the Go ecosystem. The issue involves cometbft may duplicate transactions in the mempool's data structures. Remediation is available by upgrading affected packages to version 0.34.29, 0.37.2.

CVE-2023-34451 at a Glance

CVE Identifier CVE-2023-34451
GHSA Identifier GHSA-w24w-wp77-qffm
Severity HIGH
CVSS v3.1 Base Score 8.2
CWE Classification CWE-401: Missing Release of Memory after Effective Lifetime
Affected Product Github.com/cometbft/cometbft
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 8.2

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability High (A:H)

How to Fix CVE-2023-34451

To remediate this vulnerability, upgrade all affected Github.com/cometbft/cometbft 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.34.29
Upgrade github.com/cometbft/cometbft to 0.34.29
github.com/cometbft/cometbft fixed: 0.37.2
Upgrade github.com/cometbft/cometbft to 0.37.2
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 CVE-2023-34451, inspect your project dependencies for Github.com/cometbft/cometbft:

inspect dependencies for github.com/cometbft/cometbft

Analyze the terminal output to locate any version of Github.com/cometbft/cometbft in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.34.29), 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-401: Missing Release of Memory after Effective Lifetime, where the product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse. In Github.com/cometbft/cometbft, 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

### Impact The mempool maintains two data structures to keep track of outstanding transactions: a list and a map. These two data structures are supposed to be in sync all the time in the sense that the map tracks the index (if any) of the transaction in the list. Unfortunately, it is possible to have them out of sync. When this happens, the list may contain several copies of the same transaction. Because the map tracks a single index, it is then no longer possible to remove all the copies of the transaction from the list. This happens even if the duplicated transaction is later committed in a block. The only way to remove the transaction is by restarting the node. These are the steps to cause the above duplication problem. Everything should happen within one height, that is no `FinalizeBlock` or `BeginBlock` ABCI calls should happen while these steps are reproduced: 1. send transaction tx1 to the target full node via RPC 2. send N more different transactions to the target full node, where N should be higher than the node's configured value for `cache_size` in `config.toml` 3. send transaction tx1 again to the target full node One of the copies of tx1 is now _stuck_ in the mempool's data structures. Effectively causing a memory leak, and having that node gossiping that transaction to its peers forever. The above problem can be repeated on and on until a sizable number of transactions are stuck in the mempool, in order to try to bring down the target node. This problem is present in releases: `v0.37.0`, and `v0.37.1`, as well as in `v0.34.28`, and all previous releases of the CometBFT repo. It will be fixed in releases `v0.34.29` and `v0.37.2`. ### Patches The PR containing the fix is [here](https://github.com/cometbft/cometbft/pull/890). ### Workarounds * Increasing the value of `cache_size` in `config.toml` makes it very difficult to effectively attack a full node. * Not exposing the transaction submission RPC's would mitigate the probability of a successful attack, as the attacker would then have to create a modified (byzantine) full node to be able to perform the attack via p2p. ### References * [PR](https://github.com/tendermint/tendermint/pull/2778) that introduced the map to track transactions in the mempool. * [PR](https://github.com/cometbft/cometbft/pull/890) containing the fix.

CVE-2023-34451 Affected Github.com/cometbft/cometbft Versions

2 component(s)
Fixed Versions:
0.34.290.37.2
Product / Package Ecosystem Affected Versions Fixed Version
github.com/cometbft/cometbft
Go
< 0.34.29
0.34.29
github.com/cometbft/cometbft
Go
≥ 0.37.0
< 0.37.2
0.37.2

References

Frequently Asked Questions

What is CVE-2023-34451?
CVE-2023-34451 is a security vulnerability in Github.com/cometbft/cometbft involving CometBFT may duplicate transactions in the mempool's data structures under CWE-401: Missing Release of Memory after Effective Lifetime.
Which Github.com/cometbft/cometbft versions are affected?
Affected versions include releases prior to 0.34.29, 0.37.2 across affected packages: github.com/cometbft/cometbft.
What version fixes CVE-2023-34451?
Upgrading to 0.34.29, 0.37.2 (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.34.29, 0.37.2. Upgrade your dependency to 0.34.29, 0.37.2 or later.
What is the CVSS score of CVE-2023-34451?
CVE-2023-34451 has a CVSS v3.1 base score of 8.2 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H.
What CWE is associated with CVE-2023-34451?
CVE-2023-34451 is classified under CWE-401: Missing Release of Memory after Effective Lifetime (The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.).
How can I check Go dependencies for CVE-2023-34451?
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-w24w-wp77-qffm",
  "modified" : "2023-07-05T21:34:45Z",
  "published" : "2023-07-05T21:34:45Z",
  "aliases" : [ "CVE-2023-34451" ],
  "summary" : "CometBFT may duplicate transactions in the mempool's data structures",
  "details" : "### Impact\n\nThe mempool maintains two data structures to keep track of outstanding transactions: a list and a map.\nThese two data structures are supposed to be in sync all the time in the sense that the map tracks the index (if any) of the transaction in the list. \n\nUnfortunately, it is possible to have them out of sync. When this happens, the list may contain several copies of the same transaction.\nBecause the map tracks a single index, it is then no longer possible to remove all the copies of the transaction from the list.\nThis happens  even if the duplicated transaction is later committed in a block.\nThe only way to remove the transaction is by restarting the node.\n\nThese are the steps to cause the above duplication problem. Everything should happen within one height, that is no `FinalizeBlock` or `BeginBlock` ABCI calls should happen while these steps are reproduced:\n\n1. send transaction tx1 to the target full node via RPC\n2. send N more different transactions to the target full node, where N should be higher than the node's configured value for `cache_size` in `config.toml`\n3. send transaction tx1 again to the target full node\n\nOne of the copies of tx1 is now _stuck_ in the mempool's data structures. Effectively causing a memory leak, and having that node gossiping that transaction to its peers forever.\n\nThe above problem can be repeated on and on until a sizable number of transactions are stuck in the mempool, in order to try to bring down the target node.\n\nThis problem is present in releases: `v0.37.0`, and `v0.37.1`, as well as in `v0.34.28`, and all previous releases of the CometBFT repo. It will be fixed in releases `v0.34.29` and `v0.37.2`.\n\n### Patches\n\nThe PR containing the fix is [here](https://github.com/cometbft/cometbft/pull/890).\n\n\n### Workarounds\n\n* Increasing the value of `cache_size` in `config.toml` makes it very difficult to effectively attack a full node.\n* Not exposing the transaction submission RPC's would mitigate the probability of a successful attack, as the attacker would then have to create a modified (byzantine) full node to be able to perform the attack via p2p.\n\n### References\n\n* [PR](https://github.com/tendermint/tendermint/pull/2778) that introduced the map to track transactions in the mempool.\n* [PR](https://github.com/cometbft/cometbft/pull/890) containing the fix.\n",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/cometbft/cometbft"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.34.29"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/cometbft/cometbft"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.37.0"
      }, {
        "fixed" : "0.37.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/cometbft/cometbft/security/advisories/GHSA-w24w-wp77-qffm"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-34451"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/cometbft/cometbft/pull/890"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/tendermint/tendermint/pull/2778"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/cometbft/cometbft"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-401" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-07-05T21:34:45Z",
    "nvd_published_at" : "2023-07-03T17:15:09Z"
  }
}