Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2023-23589 | First vendor Publication | 2023-01-14 |
Vendor | Cve | Last vendor Modification | 2024-11-21 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N | |||
---|---|---|---|
Overall CVSS Score | 6.5 | ||
Base Score | 6.5 | Environmental Score | 6.5 |
impact SubScore | 2.5 | Temporal Score | 6.5 |
Exploitabality Sub Score | 3.9 | ||
Attack Vector | Network | Attack Complexity | Low |
Privileges Required | None | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | Low |
Integrity Impact | Low | Availability Impact | None |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : | |||
---|---|---|---|
Cvss Base Score | N/A | Attack Range | N/A |
Cvss Impact Score | N/A | Attack Complexity | N/A |
Cvss Expoit Score | N/A | Authentication | N/A |
Calculate full CVSS 2.0 Vectors scores |
Detail
The SafeSocks option in Tor before 0.4.7.13 has a logic error in which the unsafe SOCKS4 protocol can be used but not the safe SOCKS4a protocol, aka TROVE-2022-002. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-23589 |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2024-11-28 14:21:55 |
|
2024-08-02 13:45:49 |
|
2024-08-02 01:32:17 |
|
2024-02-02 02:43:08 |
|
2024-02-01 12:29:23 |
|
2023-11-07 21:30:33 |
|
2023-09-05 13:38:46 |
|
2023-09-05 01:28:38 |
|
2023-09-02 13:36:57 |
|
2023-09-02 01:29:07 |
|
2023-08-12 13:42:30 |
|
2023-08-12 01:28:22 |
|
2023-08-11 13:33:38 |
|
2023-08-11 01:29:13 |
|
2023-08-06 13:31:01 |
|
2023-08-06 01:28:00 |
|
2023-08-04 13:31:29 |
|
2023-08-04 01:28:23 |
|
2023-07-14 13:31:19 |
|
2023-07-14 01:28:01 |
|
2023-05-03 17:27:30 |
|
2023-03-29 02:30:04 |
|
2023-03-28 12:27:49 |
|
2023-01-30 21:27:29 |
|
2023-01-28 21:27:25 |
|
2023-01-27 00:27:26 |
|
2023-01-25 00:27:21 |
|
2023-01-17 13:27:17 |
|
2023-01-14 09:27:17 |
|