dbcve.org
Bitcoin CoreApplication · Bitcoin

CVE-2012-4683

MEDIUM · 5.0 CVSS v2.0 Published 2012-09-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Unspecified vulnerability in bitcoind and Bitcoin-Qt allows attackers to cause a denial of service via unknown vectors, a different vulnerability than CVE-2012-4682.

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 · low confidence

Unspecified vulnerability in bitcoind and Bitcoin-Qt (2012 era) allows remote attackers to cause denial of service via unknown attack vectors. This is distinct from CVE-2012-4682 but shares similar characteristics of an unspecified DoS in early Bitcoin software.

MitigationUpgrade to patched Bitcoin software versions that address this vulnerability; for legacy systems, isolate from untrusted network inputs and monitor for DoS conditions.

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
Bitcoin CoreApplication
Affected:all versions

CVSS 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
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Bitcoin Core processes are running
    Check for running processes: ps aux | grep -E '(bitcoind|Bitcoin-Qt|bitcoin-qt)' or tasklist on Windows
    Affected if Either bitcoind or Bitcoin-Qt process is found running on the system
  2. Determine the Bitcoin Core version
    Run 'bitcoind -version' or 'bitcoin-qt -version' to retrieve the version number
    Affected if The version matches any Bitcoin Core release from 2011-2012 era (such as 0.4.x, 0.5.x, 0.6.x, 0.7.x series)
  3. Check RPC service exposure
    Inspect bitcoin.conf for 'rpcallowip' and 'rpcport' settings, or check if port 8332 (or 8333 for p2p) is listening on network interfaces
    Affected if RPC service is bound to 0.0.0.0 or an externally accessible IP address
  4. Verify network listening ports
    Use netstat or ss to check for listening ports: netstat -an | grep -E '(8332|8333)'
    Affected if Bitcoin daemon ports (8332 RPC, 8333 P2P) are open and reachable from untrusted networks

If Bitcoin Core (bitcoind or Bitcoin-Qt) from the 2012 era is running and exposed to network inputs, the environment is affected by this DoS vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to patched Bitcoin software versions that address this vulnerability; for legacy systems, isolate from untrusted network inputs and monitor for DoS conditions.

Fix this in Bitcoin Core Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-4683 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-4683 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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