| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in Tor up to 0.1.1.15. It has been classified as problematic. Affected by this vulnerability is an unknown functionality. This manipulation causes information disclosure. This vulnerability is registered as CVE-2011-4895. No exploit is available.
Details
A vulnerability was found in Tor up to 0.1.1.15 (Network Encryption Software). It has been declared as problematic. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. The summary by CVE is:
Tor before 0.2.2.34, when configured as a bridge, sets up circuits through a process different from the process used by a client, which makes it easier for remote attackers to enumerate bridges by observing circuit building.
The weakness was published 12/22/2011 (Website). The advisory is shared at blog.torproject.org. This vulnerability is known as CVE-2011-4895 since 12/22/2011. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Similar entries are available at VDB-59784, VDB-59783 and VDB-59782. 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
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
12/22/2011 🔍12/22/2011 🔍
12/22/2011 🔍
03/23/2015 🔍
02/13/2019 🔍
Sources
Advisory: blog.torproject.orgStatus: Not defined
Confirmation: 🔍
CVE: CVE-2011-4895 (🔍)
GCVE (CVE): GCVE-0-2011-4895
GCVE (VulDB): GCVE-100-59785
See also: 🔍
Entry
Created: 03/23/2015 16:50Updated: 02/13/2019 10:48
Changes: 03/23/2015 16:50 (45), 02/13/2019 10:48 (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.