Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2020-8516 | First vendor Publication | 2020-02-02 |
| Vendor | Cve | Last vendor Modification | 2024-04-11 |
Security-Database Scoring CVSS v3
| Cvss vector : CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | |||
|---|---|---|---|
| Overall CVSS Score | 5.3 | ||
| Base Score | 5.3 | Environmental Score | 5.3 |
| impact SubScore | 1.4 | Temporal Score | 5.3 |
| Exploitabality Sub Score | 3.9 | ||
| Attack Vector | Network | Attack Complexity | Low |
| Privileges Required | None | User Interaction | None |
| Scope | Unchanged | Confidentiality Impact | Low |
| Integrity Impact | None | Availability Impact | None |
| Calculate full CVSS 3.0 Vectors scores | |||
Security-Database Scoring CVSS v2
| Cvss vector : (AV:N/AC:L/Au:N/C:P/I:N/A:N) | |||
|---|---|---|---|
| Cvss Base Score | 5 | Attack Range | Network |
| Cvss Impact Score | 2.9 | Attack Complexity | Low |
| Cvss Expoit Score | 10 | Authentication | None Required |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
| 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. NOTE: The network team of Tor claims this is an intended behavior and not a vulnerability |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8516 |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2024-04-11 09:28:28 |
|
| 2024-03-21 09:28:30 |
|
| 2024-02-02 02:19:40 |
|
| 2024-02-01 12:21:57 |
|
| 2023-11-07 21:38:04 |
|
| 2023-09-05 13:13:59 |
|
| 2023-09-05 01:21:31 |
|
| 2023-09-02 13:12:46 |
|
| 2023-09-02 01:21:50 |
|
| 2023-08-22 13:05:06 |
|
| 2022-10-11 01:20:48 |
|
| 2022-04-18 21:23:15 |
|
| 2021-08-05 01:40:49 |
|
| 2021-07-21 17:24:34 |
|
| 2021-05-04 14:05:19 |
|
| 2021-04-22 03:10:34 |
|
| 2020-05-23 02:40:52 |
|
