{"vulnerability": "cve-2025-24371", "sightings": [{"uuid": "897243c2-29a5-4efb-9c28-5f9b2c1d7c75", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-24371", "type": "seen", "source": "https://t.me/cvedetector/17125", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-24371 - CometBFT - Byzantine Blocksync Height Manipulation\", \n  \"Content\": \"CVE ID : CVE-2025-24371 \nPublished : Feb. 3, 2025, 10:15 p.m. | 23\u00a0minutes ago \nDescription : CometBFT is a distributed, Byzantine fault-tolerant, deterministic state machine replication engine. In the `blocksync` protocol peers send their `base` and `latest` heights when they connect to a new node (`A`), which is syncing to the tip of a network. `base` acts as a lower ground and informs `A` that the peer only has blocks starting from height `base`. `latest` height informs `A` about the latest block in a network. Normally, nodes would only report increasing heights. If `B` fails to provide the latest block, `B` is removed and the `latest` height (target height) is recalculated based on other nodes `latest` heights. The existing code however doesn't check for the case where `B` first reports `latest` height `X` and immediately after height `Y`, where `X > Y`. `A` will be trying to catch up to 2000 indefinitely. This condition requires the introduction of malicious code in the full node first reporting some non-existing `latest` height, then reporting lower `latest` height and nodes which are syncing using `blocksync` protocol. This issue has been patched in versions 1.0.1 and 0.38.17 and all users are advised to upgrade. Operators may attempt to ban malicious peers from the network as a workaround. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"03 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-03T23:40:49.000000Z"}, {"uuid": "50be12e0-6be6-42e6-83d6-7f3a19d84cfa", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-24371", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113942059726528144", "content": "", "creation_timestamp": "2025-02-03T21:24:15.166052Z"}, {"uuid": "b93dd955-db29-416e-8bfb-f6233b44f510", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-24371", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhckylmsf52p", "content": "", "creation_timestamp": "2025-02-03T22:16:07.305694Z"}, {"uuid": "6f36601a-4bd2-47ac-9395-2ebf270ceb48", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-24371", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lhcxybvkfe2r", "content": "", "creation_timestamp": "2025-02-04T02:08:36.643113Z"}, {"uuid": "519af778-fe0e-4e63-8e20-5c0d51be4055", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-24371", "type": "seen", "source": "Telegram/91Y5BNIegRSylgaNZC8Ey8NRCRz2kG_oVQpna86FH9DpVLx2", "content": "", "creation_timestamp": "2025-02-06T02:40:20.000000Z"}]}