Tor up to 0.4.1.8/0.4.2.6 Daemon information disclosure ⚔ [Disputed]
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $5k-$25k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Tor up to 0.4.1.8/0.4.2.6. Impacted is an unknown function of the component Daemon. The manipulation results in information disclosure. This vulnerability is identified as CVE-2020-8516. The attack can be executed remotely. There is not any exploit available. There is ongoing doubt regarding the real existence of this vulnerability.
Details
A vulnerability classified as problematic has been found in Tor up to 0.4.1.8/0.4.2.6 (Network Encryption Software). Affected is an unknown code block of the component Daemon. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. CVE summarizes:
The daemon in Tor through 0.4.1.8 and 0.4.2.x through 0.4.2.6 does not verify that a rendezvous node is known before attempting to connect to it, which might make it easier for remote attackers to discover circuit information.
The weakness was released 02/02/2020. This vulnerability is traded as CVE-2020-8516 since 02/02/2020. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 08/04/2024). The MITRE ATT&CK project declares the attack technique as T1592.
The real existence of this vulnerability is still doubted at the moment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Name
Version
- 0.4.1.0
- 0.4.1.1
- 0.4.1.2
- 0.4.1.3
- 0.4.1.4
- 0.4.1.5
- 0.4.1.6
- 0.4.1.7
- 0.4.1.8
- 0.4.2.0
- 0.4.2.1
- 0.4.2.2
- 0.4.2.3
- 0.4.2.4
- 0.4.2.5
- 0.4.2.6
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.8VulDB Meta Temp Score: 4.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
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
02/02/2020 🔍02/02/2020 🔍
02/03/2020 🔍
08/04/2024 🔍
Sources
Advisory: 33129Status: Not defined
Disputed: 🔍
CVE: CVE-2020-8516 (🔍)
GCVE (CVE): GCVE-0-2020-8516
GCVE (VulDB): GCVE-100-149616
Entry
Created: 02/03/2020 07:52Updated: 08/04/2024 12:37
Changes: 02/03/2020 07:52 (34), 02/03/2020 07:57 (18), 03/28/2024 00:39 (18), 08/04/2024 12:37 (3)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.