CVE-2023-34451 CometBFT may duplicate transactions in the mempool's data structures
Attackers can duplicate transactions in the mempool to exhaust memory and crash nodes, requiring an upgrade to fix.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2023-34451?
CVE-2023-34451 is a high-severity denial of service vulnerability in cometbft, published on 3 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-401
Which versions are affected by CVE-2023-34451?
5 open source packages ship an affected version, including github.com/cometbft/cometbft. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/cometbft/cometbft Go | All versions | 0.34.29 |
github.com/cometbft/cometbft Go | All versions | 0.34.29 |
github.com/cometbft/cometbft Go | All versions | 0.37.2 |
github.com/cometbft/cometbft Go | From 0.37.0 | 0.37.2 |
github.com/cometbft/cometbft Go | From 0.37.0 | 0.37.2 |
Products include Cometbft Cometbft.
How do I fix CVE-2023-34451?
Upgrade github.com/cometbft/cometbft to a fixed version for your release line: 0.34.29 or 0.37.2.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2023-34451 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-34451 exists.
Other vulnerabilities in cometbft
Sources
Also known as GHSA-w24w-wp77-qffm, GO-2023-1883.