Google Tunnelblick 3.3beta20 errorExitIfAttackViaString link following

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.
2.9$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Google Tunnelblick 3.3beta20. This vulnerability affects the function errorExitIfAttackViaString. The manipulation leads to link following. This vulnerability is traded as CVE-2012-4676. There is no exploit available.

Detailsinfo

A vulnerability was found in Google Tunnelblick 3.3beta20 and classified as problematic. This issue affects the function errorExitIfAttackViaString. The manipulation with an unknown input leads to a link following vulnerability. Using CWE to declare the problem leads to CWE-59. The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. Impacted is integrity. The summary by CVE is:

The errorExitIfAttackViaString function in Tunnelblick 3.3beta20 and earlier allows local users to delete arbitrary files by constructing a (1) symlink or (2) hard link, a different vulnerability than CVE-2012-3485.

The weakness was shared 08/26/2012 (oss-sec). The advisory is shared at openwall.com. The identification of this vulnerability is CVE-2012-4676 since 08/26/2012. The exploitation is known to be difficult. An attack has to be approached locally. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries VDB-61888, VDB-61887, VDB-61886 and VDB-61885 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 2.9
VulDB Meta Temp Score: 2.9

VulDB Base Score: 2.9
VulDB Temp Score: 2.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Link following
CWE: CWE-59
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

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: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

08/26/2012 🔍
08/26/2012 +0 days 🔍
08/26/2012 +0 days 🔍
03/23/2015 +939 days 🔍
02/20/2019 +1430 days 🔍

Sourcesinfo

Vendor: google.com

Advisory: openwall.com
Status: Not defined
Confirmation: 🔍

CVE: CVE-2012-4676 (🔍)
GCVE (CVE): GCVE-0-2012-4676
GCVE (VulDB): GCVE-100-61889
See also: 🔍

Entryinfo

Created: 03/23/2015 16:50
Updated: 02/20/2019 10:57
Changes: 03/23/2015 16:50 (46), 02/20/2019 10:57 (2)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!