CVE-2011-0016
Published Jan 19, 2011 · Updated Oct 23, 2026
Original summary
Normalized public record · Updated Oct 23, 2026
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.
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- LOW
- Confidence
- Not available
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- [or-announce] 20110117 Tor 0.2.1.29 is released (security patches) ↗
- ADV-2011-0131 ↗
- gitweb.torproject.org ↗
- 42907 ↗
- blog.torproject.org ↗
- 1024980 ↗
- ADV-2011-0132 ↗
- trac.torproject.org ↗
- DSA-2148 ↗
- 42905 ↗
- [oss-security] 20110118 Re: CVE request: tor ↗
- trac.torproject.org ↗
Record history
Published Jan 19, 2011 · Last refreshed Oct 23, 2026