CVE-2024-52919
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBitcoin Core before 22.0 has a CAddrMan nIdCount integer overflow and resultant assertion failure (and daemon exit) via a flood of addr messages.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceBitcoin Core before v22.0 contains an integer overflow vulnerability in the CAddrMan address manager component. The nIdCount variable can overflow when the node receives a flood of addr messages, triggering an assertion failure that causes the daemon to exit unexpectedly.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 22.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Bitcoin Core is installedRun `bitcoind --version` or `bitcoin-cli --version` to confirm the software is present on the systemAffected if The command fails or returns an error indicating Bitcoin Core is not installed
-
Determine the installed Bitcoin Core versionExecute `bitcoind --version` (or `bitcoin-daemon --version` depending on installation) and note the version number in the outputAffected if The version returned is a release earlier than v22.0 (for example, v21.0, v0.21.x, or any release in the v0.x - v21.x series)
-
Confirm the daemon is configured to accept incoming connectionsCheck the configuration file (bitcoin.conf) or running process for settings that enable `listen=1` or allow inbound peer connectionsAffected if Inbound connections are enabled, as this allows external addr messages to reach the node and trigger the overflow condition
-
Verify the CAddrMan component is activeConfirm the node is operational and has network functionality enabled; the addr manager is active by default in normal operationAffected if The Bitcoin Core daemon is running with default network settings, as the vulnerability lies in the standard addr message processing path
The environment is affected if the installed Bitcoin Core version is any release earlier than v22.0 and the node is operating with default network settings that allow addr message processing.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped22.0
Upgrade Bitcoin Core to version 22.0 or later, which contains the fix for the nIdCount integer overflow in CAddrMan.
Bitcoin Core 22.0 or later
- 1. Back up your Bitcoin Core wallet and blockchain data before upgrading.
- 2. Download Bitcoin Core version 22.0 or later from the official Bitcoin Core website (bitcoincore.org).
- 3. Verify the downloaded binaries using the provided SHA256 checksums and GPG signatures.
- 4. Stop the running Bitcoin Core daemon (bitcoind) cleanly using 'bitcoin-cli stop'.
- 5. Install the new version, replacing the previous binaries.
- 6. Start the Bitcoin Core daemon and verify it is running without assertion failures.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52919 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-52919 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data