CVE-2010-0385 json
Tor before 0.2.1.22, and 0.2.2.x before 0.2.2.7-alpha, when functioning as a bridge directory authority, allows remote attackers to obtain…
published 2010-01-25 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-0416
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
Tor before 0.2.1.22, and 0.2.2.x before 0.2.2.7-alpha, when functioning as a bridge directory authority, allows remote attackers to obtain sensitive information about bridge identities and bridge descriptors via a dbg-stability.txt directory query.
Patch / fix
- tor Debian 14, Debian 13, Debian 12 0.2.1.22-1
debian advisories DEBIAN-CVE-2010-0385
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2010-0385 updated cvss 5.0
: tor multiple vulnerabilities in versions prior to 0.2.1.22
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.02% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
secunia.com
/advisories/38198
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/37901
vdb-entry
-
osvdb.org
/61865
vdb-entry
-
archives.seul.org
/or/announce/Jan-2010/msg00000.html
mailing-list
-
archives.seul.org
/or/talk/Jan-2010/msg00162.html
mailing-list
Sources
- CVE List CVE-2010-0385
- NVD CVE-2010-0385
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.