gsd-2023-34451
Vulnerability from gsd
Modified
2023-12-13 01:20
Details
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.
Aliases
Aliases
{
"GSD": {
"alias": "CVE-2023-34451",
"id": "GSD-2023-34451"
},
"gsd": {
"metadata": {
"exploitCode": "unknown",
"remediation": "unknown",
"reportConfidence": "confirmed",
"type": "vulnerability"
},
"osvSchema": {
"aliases": [
"CVE-2023-34451"
],
"details": "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.\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. 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.\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. 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\u0027s 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.",
"id": "GSD-2023-34451",
"modified": "2023-12-13T01:20:30.376410Z",
"schema_version": "1.4.0"
}
},
"namespaces": {
"cve.org": {
"CVE_data_meta": {
"ASSIGNER": "security-advisories@github.com",
"ID": "CVE-2023-34451",
"STATE": "PUBLIC"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "cometbft",
"version": {
"version_data": [
{
"version_affected": "=",
"version_value": "\u003c 0.34.29"
},
{
"version_affected": "=",
"version_value": "\u003e= 0.37.0, \u003c 0.37.2"
}
]
}
}
]
},
"vendor_name": "cometbft"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "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.\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. 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.\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. 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\u0027s 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."
}
]
},
"impact": {
"cvss": [
{
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.2,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H",
"version": "3.1"
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"cweId": "CWE-401",
"lang": "eng",
"value": "CWE-401: Missing Release of Memory after Effective Lifetime"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://github.com/cometbft/cometbft/security/advisories/GHSA-w24w-wp77-qffm",
"refsource": "MISC",
"url": "https://github.com/cometbft/cometbft/security/advisories/GHSA-w24w-wp77-qffm"
},
{
"name": "https://github.com/cometbft/cometbft/pull/890",
"refsource": "MISC",
"url": "https://github.com/cometbft/cometbft/pull/890"
},
{
"name": "https://github.com/tendermint/tendermint/pull/2778",
"refsource": "MISC",
"url": "https://github.com/tendermint/tendermint/pull/2778"
}
]
},
"source": {
"advisory": "GHSA-w24w-wp77-qffm",
"discovery": "UNKNOWN"
}
},
"gitlab.com": {
"advisories": [
{
"affected_range": "\u003cv0.34.29 || \u003e=v0.37.0 \u003cv0.37.2",
"affected_versions": "All versions before 0.34.29, all versions starting from 0.37.0 before 0.37.2",
"cvss_v3": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H",
"cwe_ids": [
"CWE-1035",
"CWE-401",
"CWE-937"
],
"date": "2023-07-05",
"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.\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. 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.\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. 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\u0027s 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.",
"fixed_versions": [
"v0.34.29",
"v0.37.2"
],
"identifier": "CVE-2023-34451",
"identifiers": [
"GHSA-w24w-wp77-qffm",
"CVE-2023-34451"
],
"not_impacted": "All versions starting from 0.34.29 before 0.37.0, all versions starting from 0.37.2",
"package_slug": "go/github.com/cometbft/cometbft",
"pubdate": "2023-07-05",
"solution": "Upgrade to versions 0.34.29, 0.37.2 or above.",
"title": "Missing Release of Memory after Effective Lifetime",
"urls": [
"https://github.com/cometbft/cometbft/security/advisories/GHSA-w24w-wp77-qffm",
"https://nvd.nist.gov/vuln/detail/CVE-2023-34451",
"https://github.com/cometbft/cometbft/pull/890",
"https://github.com/tendermint/tendermint/pull/2778",
"https://github.com/advisories/GHSA-w24w-wp77-qffm"
],
"uuid": "065f5531-7ffc-4c1c-991a-6fe9875b6f8f",
"versions": [
{
"commit": {
"sha": "ebd6543f759adc487b2e59c349dba1108ba7e342",
"tags": [
"v0.37.0"
],
"timestamp": "20230306171356"
},
"number": "v0.37.0"
},
{
"commit": {
"sha": "2069b41f8ce2dc7b8c5c2f2799b8636b951f3af3",
"tags": [
"v0.37.2"
],
"timestamp": "20230614201233"
},
"number": "v0.37.2"
},
{
"commit": {
"sha": "af76840cde96d35dcc08c83723ec858943e9b440",
"tags": [
"v0.34.29"
],
"timestamp": "20230614202420"
},
"number": "v0.34.29"
}
]
}
]
},
"nvd.nist.gov": {
"configurations": {
"CVE_data_version": "4.0",
"nodes": [
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:a:cometbft:cometbft:*:*:*:*:*:*:*:*",
"cpe_name": [],
"versionEndExcluding": "0.34.29",
"versionStartIncluding": "0.34.28",
"vulnerable": true
},
{
"cpe23Uri": "cpe:2.3:a:cometbft:cometbft:*:*:*:*:*:*:*:*",
"cpe_name": [],
"versionEndExcluding": "0.37.2",
"versionStartIncluding": "0.37.0",
"vulnerable": true
}
],
"operator": "OR"
}
]
},
"cve": {
"CVE_data_meta": {
"ASSIGNER": "security-advisories@github.com",
"ID": "CVE-2023-34451"
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "en",
"value": "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.\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. 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.\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. 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\u0027s 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."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "en",
"value": "CWE-401"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://github.com/cometbft/cometbft/pull/890",
"refsource": "MISC",
"tags": [
"Exploit",
"Issue Tracking",
"Patch"
],
"url": "https://github.com/cometbft/cometbft/pull/890"
},
{
"name": "https://github.com/cometbft/cometbft/security/advisories/GHSA-w24w-wp77-qffm",
"refsource": "MISC",
"tags": [
"Exploit",
"Mitigation",
"Vendor Advisory"
],
"url": "https://github.com/cometbft/cometbft/security/advisories/GHSA-w24w-wp77-qffm"
},
{
"name": "https://github.com/tendermint/tendermint/pull/2778",
"refsource": "MISC",
"tags": [
"Issue Tracking",
"Patch"
],
"url": "https://github.com/tendermint/tendermint/pull/2778"
}
]
}
},
"impact": {
"baseMetricV3": {
"cvssV3": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.2,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 4.2
}
},
"lastModifiedDate": "2023-07-17T18:58Z",
"publishedDate": "2023-07-03T17:15Z"
}
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…