CVE-2010-0384

LOWCVSS v2 · 2.12.1—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 2.1 — v2 rates that LOW (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:L/AC:L/Au:N/C:P/I:N/A:N. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 0.3% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
2.1EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS v2: 2.1Exploit: None knownExposed services: Not assessed

No fix has been recorded since the CVE record was published in 2010 — isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Tor 0.2.2.x before 0.2.2.7-alpha, when functioning as a directory mirror, does not prevent logging of the client IP address upon detection of erroneous client behavior, which might make it easier for local users to discover the identities of clients in opportunistic circumstances by reading log files.

CVSS v2.0 (legacy)
2.1LOWNVD never assigned a CVSS v3 rating to this CVE
EG Score
2.1LOWlow confidence
EG Risk
14
EG Risk 14/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity21% × 45%
The EG Score, 2.1 of 10.
Exploitation0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability30% × 15%
EchelonGraph's default before algorithm v3.4: CISA had not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix has been recorded since the CVE record was published in 2010. Isolate the affected system within your standard update timelines at low or medium mission impact and sooner than that at high (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
EPSS PROB
0.3%
EPSS %ILE
26th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).

No fix has been recorded since the CVE record was published in 2010. Isolate the affected system within your standard update timelines at low or medium mission impact and sooner than that at high (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

Published

January 25, 2010

Last Modified

April 29, 2026

References (1)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 19× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 84 of 125 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 16 repeat rows among the latest 100 are merged into the row they repeat. The 41 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 13:38 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  2. 2026-10-10 19:54 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  3. 2026-10-09 20:00 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  4. 2026-10-08 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  5. 2026-10-07 23:38 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  6. 2026-10-06 15:09 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  7. 2026-10-05 17:37 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  8. 2026-10-04 23:16 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  9. 2026-10-03 14:20 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  10. 2026-09-30 14:58 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  11. 2026-09-29 08:03 UTCEG score recompute
  12. 2026-09-27 13:39 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-09-26 15:52 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-09-24 13:57 UTCEPSS rescoreEPSS 0.4% · 25th percentile
  15. 2026-09-20 20:08 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  16. 2026-09-16 13:58 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  17. 2026-09-15 03:04 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  18. 2026-09-13 16:40 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-09-12 14:54 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  20. 2026-09-10 09:24 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-09-07 15:55 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  22. 2026-09-06 13:41 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-09-05 15:22 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  24. 2026-09-04 13:55 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  25. 2026-08-28 21:34 UTCEPSS rescoreEPSS 0.4% · 27th percentile
Show 59 more
  1. 2026-08-26 14:40 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  2. 2026-08-25 13:43 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  3. 2026-08-19 16:58 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  4. 2026-08-18 13:42 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  5. 2026-08-16 02:09 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  6. 2026-08-15 01:25 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  7. 2026-08-09 13:41 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  8. 2026-08-07 16:21 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  9. 2026-08-06 13:41 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  10. 2026-08-05 19:11 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-08-04 15:04 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  12. 2026-08-01 04:10 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  13. 2026-07-30 01:26 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  14. 2026-07-26 13:40 UTCEG score recompute▲ 2.10
  15. 2026-07-25 14:12 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  16. 2026-07-23 14:14 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-07-23 01:00 UTCEG score recompute
  18. 2026-07-23 00:38 UTCEG score recompute
  19. 2026-07-23 00:05 UTCEG score recompute
  20. 2026-07-22 21:44 UTCEG score recompute
  21. 2026-07-22 14:03 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  22. 2026-07-21 15:20 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  23. 2026-07-20 17:03 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  24. 2026-07-19 02:25 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  25. 2026-07-18 10:00 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  26. 2026-07-16 16:58 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  27. 2026-07-15 16:54 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  28. 2026-07-15 01:55 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  29. 2026-07-13 22:25 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  30. 2026-07-13 06:08 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  31. 2026-07-11 08:22 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  32. 2026-07-08 15:10 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  33. 2026-07-06 02:19 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  34. 2026-07-05 02:26 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  35. 2026-07-02 14:01 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  36. 2026-07-01 15:02 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  37. 2026-06-30 23:19 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  38. 2026-06-29 14:02 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  39. 2026-06-28 14:03 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  40. 2026-06-28 04:52 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  41. 2026-06-27 03:05 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  42. 2026-06-25 13:46 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  43. 2026-06-24 14:02 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  44. 2026-06-23 21:29 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  45. 2026-06-22 14:22 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  46. 2026-06-21 14:53 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  47. 2026-06-21 01:56 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  48. 2026-06-19 19:22 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  49. 2026-06-18 17:49 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  50. 2026-06-17 17:49 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  51. 2026-06-16 17:49 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  52. 2026-06-15 17:44 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  53. 2026-06-14 23:14 UTCEPSS rescoreEPSS <0.1% · 18th percentile
  54. 2026-06-13 22:57 UTCEPSS rescoreEPSS <0.1% · 18th percentile
  55. 2026-06-12 23:08 UTCEPSS rescoreEPSS <0.1% · 18th percentile
  56. 2026-06-11 13:56 UTCEPSS rescoreEPSS <0.1% · 18th percentile
  57. 2026-06-10 22:14 UTCEPSS rescoreEPSS <0.1% · 18th percentile
  58. 2026-06-10 13:17 UTCEPSS rescoreEPSS <0.1% · 18th percentile
  59. 2026-06-08 14:13 UTCEPSS rescoreEPSS <0.1% · 18th percentile

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2010-0384?
CVE-2010-0384 is a low-severity vulnerability; its CVE record was published on January 25, 2010. Tor 0.2.2.x before 0.2.2.7-alpha, when functioning as a directory mirror, does not prevent logging of the client IP address upon detection of erroneous client behavior, which might make it easier for local users to discover the identities of clients in opportunistic circumstances by reading log…
When was the CVE record for CVE-2010-0384 published?
The CVE record for CVE-2010-0384 was published on January 25, 2010. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 29, 2026; the record at its source may have been updated since.
Is CVE-2010-0384 actively exploited?
CVE-2010-0384 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
How do I remediate CVE-2010-0384?
No fix for CVE-2010-0384 has been recorded since its CVE record was published in 2010, and EchelonGraph holds no vendor advisory for it. Isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2010-0384

Explore →

Is Your Infrastructure Affected by CVE-2010-0384?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs