CVE-2024-52919 - Remote crash due to addr message spam (part 2)

Headline:
CVE-2024-52919 - Remote crash due to addr message spam (part 2)

Summary:
This lead was identified from Bitcoin Core Blog. It has been saved for accountability coverage and should be reviewed against the original source before expansion.

What the record says:
The source headline is: CVE-2024-52919 - Remote crash due to addr message spam (part 2). The source summary says: Disclosure of the details of an integer overflow bug which causes a crash if a node is getting spammed addr messages continuously for a very long time (years). A fix was released on April 14th 2025 in Bitcoin Core v29.0. This issue is considered Low severity. Details The address manager in Bitcoin Core uses a 32-bit identifier for each entry, incremented on every insertion. An earlier security advisory explained how it enabled an attacker to remotely trigger an assertion failure by spamming a node with addr messages until the 32-bit identifier overflow. This was partially addressed in Bitcoin Core v22.0 by rate-limiting insertions in the address manager to 1 address per peer every 10 seconds. This made the attack a lot more expensive if not impractical: even with 1000 peers continuously attacking it would still take more than a year to get the 32-bit identifier to overflow. The remaining

Why it matters:
This may be relevant to public accountability, consumer protection, government oversight, fraud monitoring, or financial transparency depending on the source record.

What is not yet proven:
This draft should not be treated as proof beyond what the linked source directly supports. Avoid adding accusations, private information, or copied text from the original source.

Source:
https://bitcoincore.org/en/2025/04/28/disclose-cve-2024-52919/

AI writer note: OPENAI_API_KEY is empty, so this was generated with the built-in safe fallback writer.