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.
References
Link | Resource |
---|---|
https://github.com/cometbft/cometbft/pull/890 | Exploit Issue Tracking Patch |
https://github.com/cometbft/cometbft/security/advisories/GHSA-w24w-wp77-qffm | Exploit Mitigation Vendor Advisory |
https://github.com/tendermint/tendermint/pull/2778 | Issue Tracking Patch |
https://github.com/cometbft/cometbft/pull/890 | Exploit Issue Tracking Patch |
https://github.com/cometbft/cometbft/security/advisories/GHSA-w24w-wp77-qffm | Exploit Mitigation Vendor Advisory |
https://github.com/tendermint/tendermint/pull/2778 | Issue Tracking Patch |
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 08:07
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/cometbft/cometbft/pull/890 - Exploit, Issue Tracking, Patch | |
References | () https://github.com/cometbft/cometbft/security/advisories/GHSA-w24w-wp77-qffm - Exploit, Mitigation, Vendor Advisory | |
References | () https://github.com/tendermint/tendermint/pull/2778 - Issue Tracking, Patch |
17 Jul 2023, 18:58
Type | Values Removed | Values Added |
---|---|---|
CPE | cpe:2.3:a:cometbft:cometbft:*:*:*:*:*:*:*:* | |
CVSS |
v2 : v3 : |
v2 : unknown
v3 : 8.2 |
First Time |
Cometbft
Cometbft cometbft |
|
References | (MISC) https://github.com/cometbft/cometbft/security/advisories/GHSA-w24w-wp77-qffm - Exploit, Mitigation, Vendor Advisory | |
References | (MISC) https://github.com/tendermint/tendermint/pull/2778 - Issue Tracking, Patch | |
References | (MISC) https://github.com/cometbft/cometbft/pull/890 - Exploit, Issue Tracking, Patch |
03 Jul 2023, 17:15
Type | Values Removed | Values Added |
---|---|---|
New CVE |
Information
Published : 2023-07-03 17:15
Updated : 2024-11-21 08:07
NVD link : CVE-2023-34451
Mitre link : CVE-2023-34451
CVE.ORG link : CVE-2023-34451
JSON object : View
Products Affected
cometbft
- cometbft
CWE
CWE-401
Missing Release of Memory after Effective Lifetime