Google Tunnelblick 3.3beta20 errorExitIfAttackViaString link following
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.9 | $0-$5k | 0.00 |
Summary
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.
Details
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. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/20/2019).
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.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.9VulDB Meta Temp Score: 2.9
VulDB Base Score: 2.9
VulDB Temp Score: 2.9
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: Link followingCWE: 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-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
08/26/2012 🔍08/26/2012 🔍
08/26/2012 🔍
03/23/2015 🔍
02/20/2019 🔍
Sources
Vendor: google.comAdvisory: openwall.com
Status: Not defined
Confirmation: 🔍
CVE: CVE-2012-4676 (🔍)
GCVE (CVE): GCVE-0-2012-4676
GCVE (VulDB): GCVE-100-61889
See also: 🔍
Entry
Created: 03/23/2015 16:50Updated: 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.
No comments yet. Languages: en.
Please log in to comment.