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.
References
Link | Resource |
---|---|
https://gitlab.torproject.org/tpo/core/tor/-/commit/a282145b3634547ab84ccd959d0537c021ff7ffc | Patch Vendor Advisory |
https://gitlab.torproject.org/tpo/core/tor/-/issues/40730 | Exploit Issue Tracking Patch Vendor Advisory |
https://gitlab.torproject.org/tpo/core/tor/-/raw/release-0.4.7/ReleaseNotes | Release Notes Vendor Advisory |
https://www.debian.org/security/2023/dsa-5320 | Third Party Advisory |
https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZMY4FWXYKP3MDXTZ3EJ7XJVGBCKBK2XL/ | Mailing List Third Party Advisory |
https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IYOLTP6HQO2HPXUYKOR7P5YYYN7CINQQ/ | Mailing List Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2023/01/msg00026.html | Mailing List Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Information
Published : 2023-01-13 17:15
Updated : 2023-01-30 07:16
NVD link : CVE-2023-23589
Mitre link : CVE-2023-23589
JSON object : View
CWE
Products Affected
debian
- debian_linux
fedoraproject
- fedora
torproject
- tor