CVE-2011-0016

UnknownEPSS 0.40%

Last modified

CVE-2011-0016 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.40% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
0.40%

31.8th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
TorTor<= 0.2.1.28—
TorTor0.0.2—
TorTor0.0.2_pre13—
TorTor0.0.2_pre14—
TorTor0.0.2_pre15—
TorTor0.0.2_pre16—
TorTor0.0.2_pre17—
TorTor0.0.2_pre18—
TorTor0.0.2_pre19—
TorTor0.0.2_pre20—
TorTor0.0.2_pre21—
TorTor0.0.2_pre22—
TorTor0.0.2_pre23—
TorTor0.0.2_pre24—
TorTor0.0.2_pre25—
TorTor0.0.2_pre26—
TorTor0.0.2_pre27—
TorTor0.0.3—
TorTor0.0.4—
TorTor0.0.5—
TorTor0.0.6—
TorTor0.0.6.1—
TorTor0.0.6.2—
TorTor0.0.7—
TorTor0.0.7.1—
TorTor0.0.7.2—
TorTor0.0.7.3—
TorTor0.0.8—
TorTor0.0.8.1—
TorTor0.0.9—
TorTor0.0.9.1—
TorTor0.0.9.2—
TorTor0.0.9.3—
TorTor0.0.9.4—
TorTor0.0.9.5—
TorTor0.0.9.6—
TorTor0.0.9.7—
TorTor0.0.9.8—
TorTor0.0.9.9—
TorTor0.0.9.10—
TorTor0.1.0.1—
TorTor0.1.0.2—
TorTor0.1.0.3—
TorTor0.1.0.4—
TorTor0.1.0.5—
TorTor0.1.0.6—
TorTor0.1.0.7—
TorTor0.1.0.8—
TorTor0.1.0.9—
TorTor0.1.0.10—

Showing 50 of 186 affected configurations. See NVD for the full list.

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2011-0016?
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.
How severe is CVE-2011-0016?
Severity scoring for CVE-2011-0016 is pending analysis. The EPSS model estimates a 0.40% probability of exploitation in the next 30 days.
How do I fix CVE-2011-0016?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2011

Are you affected by CVE-2011-0016?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST