The Tor Project
Tor
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at tor, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2015-2688 | 24 Jan 2020 | before 0.2.4.26; 0.2.5.x before 0.2.5.11 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2015-2689 | 24 Jan 2020 | before 0.2.4.26; 0.2.5.x before 0.2.5.11 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2015-2929 | 24 Jan 2020 | before 0.2.4.27; 0.2.5.x before 0.2.5.12; 0.2.6.x before 0.2.6.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2015-2928 | 24 Jan 2020 | before 0.2.4.27; 0.2.5.x before 0.2.5.12; 0.2.6.x before 0.2.6.7 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.