CVE-2010-0383: Tor before 0.2.1.22, and 0.2.2.x before 0.2.2.7-alpha, uses deprecated identity keys for certain directory aut

Routine

MEDIUM 5.0DOWNGRADE

CVE-2010-0383 is a medium-severity flaw (CVSS 5.0) affecting tor. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	1.7% (top 23%)
CISA exploited list	No
Weakness	CWE-200
Published	2010-01-25
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: tor

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2010-01-25 19:30 UTCPublished CVE record published
2026-06-16 23:16 UTCUpdated Record last modified

tor tor DOWNGRADE

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

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.0.2

1. Check installed version

apt-cache policy tor || rpm -q tor || tor --version

2. No fixed release: DOWNGRADE to a release before 0.0.2 (Debian / Ubuntu)

apt-cache madison tor sudo apt install tor=<VERSION_BEFORE_0.0.2> sudo apt-mark hold tor

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list tor sudo dnf downgrade tor-<VERSION_BEFORE_0.0.2> sudo dnf versionlock add tor

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2010-0383?

tor: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2010-0383 being exploited?

CVE-2010-0383 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2010-0383 affect?

CVE-2010-0383 affects tor. Severity is medium (CVSS 5.0). 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.

How urgent is CVE-2010-0383?

Priority 37/100. No elevated risk signals yet.

Related CVEs

CVE-2026-44603 LOW 3.7 UPGRADE Tor before 0.4.9.7 has an out-of-bounds read by one byte via a malformed BEGIN cell, aka TROVE-2026-007.
CVE-2026-44597 LOW 3.7 UPGRADE Tor before 0.4.9.7 has an out-of-bounds read when an END, a TRUNCATE, or a TRUNCATED cell lacks a reason in it
CVE-2026-44600 LOW 3.7 UPGRADE Tor before 0.4.9.7 mishandles accounting of the conflux out-of-order queue during the clearing of a queue, aka
CVE-2026-44601 LOW 3.7 UPGRADE Tor before 0.4.9.7, when circuit queue memory pressure exists, can experience a client crash because of a doub
CVE-2026-44602 LOW 3.7 UPGRADE Tor before 0.4.9.7 has a NULL pointer dereference when a CERT cell is received out of order, aka TROVE-2026-00

References

← Back to latest CVEs