CVE-2011-0016

What it is

Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha does not properly manage key data in memory, which might allow local users to obtain sensitive information by leveraging the ability to read memory that was previously used by a different process.

At a glance

Exploitability

Can be exploited locally on the machine without logging in. Limited direct impact.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2011-01-19 12:00 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:26 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 2.1 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2011-01-19 12:00 UTC

Last modified

2026-06-16 23:26 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-399

Record status

Modified

Affected

• Tor ≤ 0.2.1.28
• Tor 0.0.2
• Tor 0.0.2_pre13
• Tor 0.0.2_pre14
• Tor 0.0.2_pre15
• Tor 0.0.2_pre16
• Tor 0.0.2_pre17
• Tor 0.0.2_pre18

Attack profile CVSS 2.0 · 2.1

Attack vector

Local

Complexity

Low

Authentication

None

Confidentiality

Partial

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2011-0016.md and follow it. Check whether this project is affected by CVE-2011-0016. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge