PatchTheCVEtor project vulnerabilities
Recent CVEs affecting tor project products. 5 tracked.
tor project has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 5. Most recent: 2017-12-03. Highest priority: CVE-2017-8823 (score 57/100).
- CVE-2017-8823 HIGH 8.1 UPGRADE MITIGATE In Tor before 0.2.5.16, 0.2.6 through 0.2.8 before 0.2.8.17, 0.2.9 before 0.2.9.14, 0.3.0 before 0.3.0.13, and
- CVE-2017-8822 LOW 3.7 UPGRADE MITIGATE In Tor before 0.2.5.16, 0.2.6 through 0.2.8 before 0.2.8.17, 0.2.9 before 0.2.9.14, 0.3.0 before 0.3.0.13, and
- CVE-2017-8821 HIGH 7.5 UPGRADE MITIGATE In Tor before 0.2.5.16, 0.2.6 through 0.2.8 before 0.2.8.17, 0.2.9 before 0.2.9.14, 0.3.0 before 0.3.0.13, and
- CVE-2017-8820 HIGH 7.5 UPGRADE MITIGATE In Tor before 0.2.5.16, 0.2.6 through 0.2.8 before 0.2.8.17, 0.2.9 before 0.2.9.14, 0.3.0 before 0.3.0.13, and
- CVE-2017-8819 HIGH 7.5 UPGRADE MITIGATE In Tor before 0.2.5.16, 0.2.6 through 0.2.8 before 0.2.8.17, 0.2.9 before 0.2.9.14, 0.3.0 before 0.3.0.13, and
FAQ
How do I fix tor project vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is tor project being exploited right now?
None of the tracked tor project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which tor project CVE should I patch first?
CVE-2017-8823 currently ranks highest (57/100): In Tor before 0.2.5.16, 0.2.6 through 0.2.8 before 0.2.8.17, 0.2.9 before 0.2.9.14, 0.3.0 before 0.3.0.13, and.