Security readout for executives and security teams
Plain-English summary
Bitcoin Core nodes before 24.0.1 could be crashed remotely by sending many low-difficulty header chains. The business impact is availability loss: disrupted node operation, monitoring noise, and possible service interruption for organizations depending on their own Bitcoin infrastructure.
Executive priority
Treat as high priority where Bitcoin Core supports business operations. The vulnerability affects availability, not funds directly, but node outages can disrupt transaction monitoring, wallet services, mining operations, and operational confidence.
Technical view
The issue is a resource-allocation flaw: affected nodes stored presented header chains before confirming the chain had enough work. A remote unauthenticated attacker could trigger excessive memory use and crash the daemon. CVSS 3.1 is 7.5, availability-only, network exploitable, and low complexity.
Likely exposure
Exposure is most likely for organizations running Bitcoin Core before 24.0.1, especially internet-reachable full nodes supporting exchanges, custodians, mining, wallets, or internal blockchain services.
Exploitation context
The provided bundle does not show CISA KEV listing or confirmed active exploitation. Public descriptions identify a denial-of-service condition through flooding low-difficulty header chains, but no source here establishes real-world attacks.
Researcher notes
Classified as CWE-770. The key technical condition is storing header chains before sufficient-work validation. Affected product metadata is sparse in the bundle, but the CVE description specifically names Bitcoin Core before 24.0.1.
Mitigation direction
- Upgrade Bitcoin Core nodes to 24.0.1 or later.
- Prioritize public or business-critical nodes running pre-24.0.1 versions.
- Review Bitcoin Core disclosure guidance for any operational recommendations.
- Monitor node memory, crashes, and restart frequency after remediation.
Validation and detection
- Inventory all Bitcoin Core nodes and record exact versions.
- Confirm no production node runs a version before 24.0.1.
- Review daemon logs for unexplained crashes or memory exhaustion.
- Verify monitoring alerts cover node availability and resource pressure.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2019-25220 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.