Security readout for executives and security teams
Plain-English summary
This CVE affects very old Bitcoin client software. A specially formed Bitcoin transaction could crash wxBitcoin or bitcoind before version 0.3.5, causing service downtime rather than data theft. Business urgency depends on whether any legacy Bitcoin nodes still run in production or exposed environments.
Executive priority
Prioritize this if the organization operates legacy Bitcoin infrastructure or maintains old cryptocurrency systems. For organizations without pre-0.3.5 wxBitcoin or bitcoind, business risk appears low based on the provided evidence.
Technical view
wxBitcoin and bitcoind before 0.3.5 can be remotely crashed by a Bitcoin transaction containing an OP_LSHIFT script opcode. The provided sources describe denial of service only. No CVSS, CWE, CPE, patch advisory, or active exploitation evidence is included in the bundle.
Likely exposure
Exposure is likely limited to legacy wxBitcoin or bitcoind deployments earlier than 0.3.5. Modern Bitcoin Core deployments are not identified as affected in the provided sources. Asset inventories should focus on historical binaries, archived systems, labs, and forgotten nodes.
Exploitation context
The source bundle supports remote denial of service through a crafted Bitcoin transaction. It does not cite active exploitation, KEV listing, public weaponization, authentication requirements, or broader compromise impact. Treat exploitation status as unconfirmed beyond the described crash condition.
Researcher notes
Metadata is sparse: no CVSS, CWE, CPE, or detailed vendor advisory is included. The affected range and crash trigger come from the CVE description and Bitcoin Wiki reference. Avoid expanding scope beyond wxBitcoin and bitcoind before 0.3.5.
Mitigation direction
- Inventory any wxBitcoin or bitcoind installations and record exact versions.
- Retire or upgrade any instance older than 0.3.5.
- Check Bitcoin project guidance before making production changes.
- Remove unsupported legacy nodes from exposed networks.
- Monitor legacy nodes for unexplained daemon crashes or restarts.
Validation and detection
- Confirm whether wxBitcoin or bitcoind exists in asset inventories.
- Verify installed versions are not earlier than 0.3.5.
- Check externally reachable hosts for legacy Bitcoin node exposure.
- Review operational logs for recurring daemon crash patterns.
- Document any compensating controls for unsupported legacy nodes.
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.
CVE-2010-5137 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://en.bitcoin.it/wiki/CVEsCVE reference · x_refsource_CONFIRM
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.