| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Tor up to 0.1.1.19. This affects an unknown function. The manipulation leads to denial of service. This vulnerability is listed as CVE-2006-3416. There is no available exploit. The actual existence of this vulnerability is currently in question. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Tor up to 0.1.1.19 (Network Encryption Software). It has been rated as problematic. This issue affects an unknown functionality. The manipulation with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability. The summary by CVE is:
** DISPUTED ** Tor before 0.1.1.20 kills the circuit when it receives an unrecognized relay command, which causes network circuits to be disbanded. NOTE: while this item is listed under the "Security fixes" section of the developer changelog, the developer clarified on 20060707 that this is only a self-DoS. Therefore this issue should not be included in CVE.
The weakness was presented 07/06/2006 (Website). The advisory is shared at secunia.com. The identification of this vulnerability is CVE-2006-3416 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. Neither technical details nor an exploit are publicly available.
The real existence of this vulnerability is still doubted at the moment.
Upgrading to version 0.1.1.20 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Secunia (SA20514†). See VDB-31196, VDB-31195, VDB-31194 and VDB-31192 for similar entries. Several companies clearly confirm that VulDB is the primary source for best 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: Denial of serviceCWE: CWE-404
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
07/06/2006 🔍07/06/2006 🔍
07/06/2006 🔍
03/12/2015 🔍
08/07/2024 🔍
Sources
Advisory: secunia.com⛔Status: Not defined
Confirmation: 🔍
Disputed: 🔍
CVE: CVE-2006-3416 (🔍)
GCVE (CVE): GCVE-0-2006-3416
GCVE (VulDB): GCVE-100-31193
Secunia: 20514
See also: 🔍
Entry
Created: 03/12/2015 14:25Updated: 08/07/2024 23:10
Changes: 03/12/2015 14:25 (48), 08/14/2018 08:27 (3), 08/07/2024 23:10 (17)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.