VDB-31189 · CVE-2006-3412 · SA20514

Tor up to 0.1.1.19 Access Restriction

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.2$0-$5k0.00

Summaryinfo

A vulnerability marked as critical has been reported in Tor up to 0.1.1.19. This issue affects some unknown processing of the component Access Restriction. This manipulation causes an unknown weakness. The identification of this vulnerability is CVE-2006-3412. There is no exploit available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability has been found in Tor up to 0.1.1.19 (Network Encryption Software) and classified as critical. Affected by this vulnerability is an unknown code of the component Access Restriction. As an impact it is known to affect confidentiality, and integrity. The summary by CVE is:

Tor before 0.1.1.20 does not sufficiently obey certain firewall options, which allows remote attackers to bypass intended access restrictions for dirservers, direct connections, or proxy servers.

The weakness was shared 05/24/2006 (Website). The advisory is shared at security.gentoo.org. This vulnerability is known as CVE-2006-3412 since 07/06/2006. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.

Upgrading to version 0.1.1.20 eliminates this vulnerability.

The vulnerability is also documented in the databases at OSVDB (25874†) and Secunia (SA20514†). The entries VDB-31196, VDB-31195, VDB-31194 and VDB-31193 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.2

VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Unknown
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Tor 0.1.1.20

Timelineinfo

05/24/2006 🔍
05/24/2006 +0 days 🔍
06/08/2006 +14 days 🔍
07/06/2006 +28 days 🔍
07/06/2006 +0 days 🔍
03/12/2015 +3171 days 🔍
07/31/2018 +1237 days 🔍

Sourcesinfo

Advisory: security.gentoo.org
Status: Not defined
Confirmation: 🔍

CVE: CVE-2006-3412 (🔍)
GCVE (CVE): GCVE-0-2006-3412
GCVE (VulDB): GCVE-100-31189
Secunia: 20514 - Gentoo update for tor, Moderately Critical
OSVDB: 25874 - EFF Tor Firewall Restriction Bypass Persistance

See also: 🔍

Entryinfo

Created: 03/12/2015 14:25
Updated: 07/31/2018 05:41
Changes: 03/12/2015 14:25 (54), 07/31/2018 05:41 (1)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!