DEBIAN-CVE-2023-23589

See a problem?
Please try reporting it to the source first.
Source
https://security-tracker.debian.org/tracker/CVE-2023-23589
Import Source
https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2023-23589.json
JSON Data
https://api.osv.dev/v1/vulns/DEBIAN-CVE-2023-23589
Upstream
Published
2023-01-14T01:15:15Z
Modified
2025-09-25T03:27:58.388651Z
Summary
[none]
Details

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

Affected packages

Debian:11 / tor

Package

Name
tor
Purl
pkg:deb/debian/tor?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
0.4.5.16-1

Affected versions

0.*

0.4.5.9-1
0.4.5.10-1~bpo10+1
0.4.5.10-1~deb11u1
0.4.5.10-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:12 / tor

Package

Name
tor
Purl
pkg:deb/debian/tor?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
0.4.7.13-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:13 / tor

Package

Name
tor
Purl
pkg:deb/debian/tor?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
0.4.7.13-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}

Debian:14 / tor

Package

Name
tor
Purl
pkg:deb/debian/tor?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
0.4.7.13-1

Ecosystem specific 

{
    "urgency": "not yet assigned"
}