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.
{ "binaries": [ { "binary_name": "tor", "binary_version": "0.2.4.27-1ubuntu0.1+esm2" }, { "binary_name": "tor-geoipdb", "binary_version": "0.2.4.27-1ubuntu0.1+esm2" } ] }
"https://github.com/canonical/ubuntu-security-notices/blob/main/osv/cve/2023/UBUNTU-CVE-2023-23589.json"
{ "binaries": [ { "binary_name": "tor", "binary_version": "0.2.9.14-1ubuntu1~16.04.3+esm1" }, { "binary_name": "tor-geoipdb", "binary_version": "0.2.9.14-1ubuntu1~16.04.3+esm1" } ] }
{ "binaries": [ { "binary_name": "tor", "binary_version": "0.3.2.10-1ubuntu0.2~esm2" }, { "binary_name": "tor-geoipdb", "binary_version": "0.3.2.10-1ubuntu0.2~esm2" } ] }
{ "binaries": [ { "binary_name": "tor", "binary_version": "0.4.2.7-1ubuntu0.1~esm1" }, { "binary_name": "tor-geoipdb", "binary_version": "0.4.2.7-1ubuntu0.1~esm1" } ] }
{ "binaries": [ { "binary_name": "tor", "binary_version": "0.4.6.10-1" }, { "binary_name": "tor-geoipdb", "binary_version": "0.4.6.10-1" } ] }