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.
The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.
Link | Tags |
---|---|
https://gitlab.torproject.org/tpo/core/tor/-/raw/release-0.4.7/ReleaseNotes | release notes vendor advisory |
https://gitlab.torproject.org/tpo/core/tor/-/issues/40730 | patch exploit vendor advisory issue tracking |
https://gitlab.torproject.org/tpo/core/tor/-/commit/a282145b3634547ab84ccd959d0537c021ff7ffc | patch vendor advisory |
https://www.debian.org/security/2023/dsa-5320 | third party advisory vendor advisory |
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZMY4FWXYKP3MDXTZ3EJ7XJVGBCKBK2XL/ | vendor advisory |
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/IYOLTP6HQO2HPXUYKOR7P5YYYN7CINQQ/ | vendor advisory |
https://lists.debian.org/debian-lts-announce/2023/01/msg00026.html | third party advisory mailing list |
https://security.gentoo.org/glsa/202305-11 | vendor advisory |