Tor

Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname configuration option, uses the local hostname as the Nickname value, which allows remote attackers to obtain potentially sensitive information by reading this value.

Published: 2011-12-23T02:00:00.000Z
Updated: 2024-09-16T16:53:14.667Z

Tor before 0.2.2.24-alpha continues to use a reachable bridge that was previously configured but is not currently configured, which might allow remote attackers to obtain sensitive information about clients in opportunistic circumstances by monitoring network traffic to the bridge port.

Published: 2011-12-23T02:00:00.000Z
Updated: 2024-09-16T18:28:19.118Z

Tor before 0.2.2.34, when configured as a bridge, sets up circuits through a process different from the process used by a client, which makes it easier for remote attackers to enumerate bridges by observing circuit building.

Published: 2011-12-23T02:00:00.000Z
Updated: 2024-09-17T01:55:32.706Z

Tor before 0.2.2.34, when configured as a bridge, uses direct DirPort access instead of a Tor TLS connection for a directory fetch, which makes it easier for remote attackers to enumerate bridges by observing DirPort connections.

Published: 2011-12-23T02:00:00.000Z
Updated: 2024-09-16T20:48:21.454Z

Multiple heap-based buffer overflows in Tor before 0.2.2.35 allow remote attackers to cause a denial of service (memory corruption) or possibly execute arbitrary code by (1) establishing a SOCKS connection to SocksPort or (2) leveraging a SOCKS proxy configuration.

Published: 2011-12-23T02:00:00.000Z
Updated: 2024-08-06T23:15:31.127Z