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 0.2.0.28, and probably 0.2.0.34 and earlier, allows remote attackers, with control of an entry router and an exit router, to confirm that a sender and receiver are communicating via vectors involving (1) replaying, (2) modifying, (3) inserting, or (4) deleting a single cell, and then observing cell recognition errors at the exit router. NOTE: the vendor disputes the significance of this issue, noting that the product's design "accepted end-to-end correlation as an attack that is too expensive to solve."

Published: 2009-02-20T19:00:00.000Z
Updated: 2024-09-17T03:13:48.226Z

Unspecified vulnerability in Tor before 0.2.0.33 has unspecified impact and remote attack vectors that trigger heap corruption.

Published: 2009-02-03T23:00:00.000Z
Updated: 2024-08-07T04:31:26.160Z