| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Tor up to 0.1.1.19. This affects an unknown part. The manipulation leads to information disclosure. This vulnerability is uniquely identified as CVE-2006-3410. No exploit exists. You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in Tor up to 0.1.1.19 (Network Encryption Software). This issue affects some unknown functionality. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:
Tor before 0.1.1.20 creates "internal circuits" primarily consisting of nodes with "useful exit nodes," which allows remote attackers to conduct unspecified statistical attacks.
The weakness was disclosed 05/24/2006 (Website). It is possible to read the advisory at security.gentoo.org. The identification of this vulnerability is CVE-2006-3410 since 07/06/2006. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
Upgrading to version 0.1.1.20 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (26798), SecurityFocus (BID 18323†), OSVDB (25882†) and Secunia (SA20277†). The entries VDB-28469, VDB-31398, VDB-31196 and VDB-31195 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
- 0.1.1.0
- 0.1.1.1
- 0.1.1.2
- 0.1.1.3
- 0.1.1.4
- 0.1.1.5
- 0.1.1.6
- 0.1.1.7
- 0.1.1.8
- 0.1.1.9
- 0.1.1.10
- 0.1.1.11
- 0.1.1.12
- 0.1.1.13
- 0.1.1.14
- 0.1.1.15
- 0.1.1.16
- 0.1.1.17
- 0.1.1.18
- 0.1.1.19
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Tor 0.1.1.20
Timeline
05/24/2006 🔍05/24/2006 🔍
05/25/2006 🔍
07/06/2006 🔍
07/06/2006 🔍
07/10/2006 🔍
03/12/2015 🔍
07/30/2018 🔍
Sources
Advisory: security.gentoo.orgStatus: Confirmed
Confirmation: 🔍
CVE: CVE-2006-3410 (🔍)
GCVE (CVE): GCVE-0-2006-3410
GCVE (VulDB): GCVE-100-31187
X-Force: 26798 - Tor circuits information disclosure
SecurityFocus: 18323 - Trac Information Disclosure And Denial of Service Vulnerabilities
Secunia: 20277 - Tor Weakness and Multiple Vulnerabilities, Moderately Critical
OSVDB: 25882 - EFF Tor Internal Circuit Handling Unspecified Weakness
See also: 🔍
Entry
Created: 03/12/2015 14:25Updated: 07/30/2018 08:15
Changes: 03/12/2015 14:25 (56), 07/30/2018 08:15 (7)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.