Security readout for executives and security teams
Plain-English summary
CVE-2013-2273 is a privacy issue in old bitcoind and Bitcoin-Qt releases. Certain Bitcoin transaction outputs were predictable enough that a remote observer could more easily identify returned change, potentially exposing sensitive wallet activity patterns.
Executive priority
Prioritize if the organization still operates legacy Bitcoin infrastructure or has privacy-sensitive wallet history from 2013-era clients. Otherwise, this is mainly a legacy hygiene and historical privacy review item.
Technical view
Affected bitcoind and Bitcoin-Qt branches before the listed 0.4.9rc1, 0.5.8rc1, 0.6.0.11rc1, 0.6.5rc1, and 0.7.3rc1 releases had predictable transaction outputs. The weakness could help remote attackers infer which output was change.
Likely exposure
Exposure is likely limited to legacy Bitcoin nodes or wallets still running the affected historical bitcoind or Bitcoin-Qt versions. The supplied sources do not identify affected CPEs or modern maintained products.
Exploitation context
The sources describe remote information disclosure risk, not code execution or fund theft. CISA KEV status is false, and the bundle provides no evidence of active exploitation.
Researcher notes
Evidence is sparse: no CVSS, CWE, CPE, or detailed patch notes are included in the bundle. The core issue is transaction change-output predictability, so validation should focus on version exposure and historical wallet use.
Mitigation direction
- Inventory any bitcoind or Bitcoin-Qt deployments and record exact versions.
- Upgrade affected branches to the referenced fixed release candidate or later maintained release.
- Consult Bitcoin project CVE guidance before operating legacy wallet software.
- Treat historical transactions from vulnerable clients as potentially less private.
Validation and detection
- Confirm no running instance is below the fixed version for its branch.
- Check asset inventories, backups, and cold systems for legacy Bitcoin-Qt or bitcoind binaries.
- Review wallet operational records for transactions created by vulnerable versions.
- Document residual privacy exposure where historical transactions cannot be changed.
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-2013-2273 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.