Vulnerabilities > TOR > TOR > 0.2.1.12
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2011-12-23 | CVE-2011-4897 | Information Exposure vulnerability in 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. | 4.3 |
| 2011-12-23 | CVE-2011-4896 | Information Exposure vulnerability in TOR 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. | 4.3 |
| 2011-12-23 | CVE-2011-4895 | Information Exposure vulnerability in TOR 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. | 4.3 |
| 2011-12-23 | CVE-2011-4894 | Information Exposure vulnerability in TOR 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. | 4.3 |
| 2011-12-23 | CVE-2011-2778 | Improper Restriction of Operations Within the Bounds of A Memory Buffer vulnerability in TOR 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. | 7.6 |
| 2011-12-23 | CVE-2011-2769 | Information Exposure vulnerability in TOR Tor before 0.2.2.34, when configured as a bridge, accepts the CREATE and CREATE_FAST values in the Command field of a cell within an OR connection that it initiated, which allows remote relays to enumerate bridges by using these values. | 4.3 |
| 2011-12-23 | CVE-2011-2768 | Permissions, Privileges, and Access Controls vulnerability in TOR Tor before 0.2.2.34, when configured as a client or bridge, sends a TLS certificate chain as part of an outgoing OR connection, which allows remote relays to bypass intended anonymity properties by reading this chain and then determining the set of entry guards that the client or bridge had selected. | 5.8 |
| 2011-06-14 | CVE-2011-1924 | Improper Restriction of Operations Within the Bounds of A Memory Buffer vulnerability in TOR Buffer overflow in the policy_summarize function in or/policies.c in Tor before 0.2.1.30 allows remote attackers to cause a denial of service (directory authority crash) via a crafted policy that triggers creation of a long port list. | 5.0 |
| 2011-01-19 | CVE-2011-0493 | Numeric Errors vulnerability in TOR Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha might allow remote attackers to cause a denial of service (assertion failure and daemon exit) via vectors related to malformed router caches and improper handling of integer values. | 5.0 |
| 2011-01-19 | CVE-2011-0492 | Resource Management Errors vulnerability in TOR Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha allows remote attackers to cause a denial of service (assertion failure and daemon exit) via blobs that trigger a certain file size, as demonstrated by the cached-descriptors.new file. | 5.0 |