dbcve.org
TorApplication

CVE-2010-0383

MEDIUM · 5.0 CVSS v2.0 Published 2010-01-25
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
Tor before 0.2.1.22, and 0.2.2.x before 0.2.2.7-alpha, uses deprecated identity keys for certain directory authorities, which makes it easier for man-in-the-middle attackers to compromise the anonymity of traffic sources and destinations.

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

This vulnerability affects Tor versions before 0.2.1.22 and 0.2.2.x before 0.2.2.7-alpha. The issue is that certain directory authorities used deprecated identity keys, which are weaker cryptographic keys that should have been replaced. This allowed man-in-the-middle attackers to potentially compromise the anonymity of Tor traffic by intercepting or manipulating the directory authority communications that inform clients about the network topology.

MitigationUpgrade to Tor version 0.2.1.22 or later, or version 0.2.2.7-alpha or later, which contain the corrected directory authority identity keys.

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
TorApplication
Affected:= 0.0.2= 0.0.2_pre13= 0.0.2_pre14= 0.0.2_pre15= 0.0.2_pre16= 0.0.2_pre17= 0.0.2_pre18= 0.0.2_pre19= 0.0.2_pre20= 0.0.2_pre21= 0.0.2_pre22= 0.0.2_pre23

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
Partial
Integrity
None
Availability
None

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

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. Check installed Tor version
    Run 'tor --version' or check the Tor package version installed on your system
    Affected if The version is before 0.2.1.22 or is 0.2.2.x before 0.2.2.7-alpha
  2. Verify Tor is running
    Check if the Tor process is active using 'ps aux | grep tor' or check service status
    Affected if Tor is running and the version meets the affected criteria from step 1
  3. Inspect Tor configuration for directory authorities
    Examine torrc configuration file for custom DirectoryAuthority entries or default authority settings
    Affected if Custom directory authorities are configured that may be using deprecated identity keys

Your environment is affected if you are running a Tor version before 0.2.1.22 or 0.2.2.x before 0.2.2.7-alpha and actively connecting to the Tor network via directory authorities.

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 Tor version 0.2.1.22 or later, or version 0.2.2.7-alpha or later, which contain the corrected directory authority identity keys.

Fix this in Tor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0383 — 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-2010-0383 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