Vulnerabilities > TOR > TOR > 0.1.1.8.alpha
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2010-12-22 | CVE-2010-1676 | Improper Restriction of Operations Within the Bounds of A Memory Buffer vulnerability in TOR Heap-based buffer overflow in Tor before 0.2.1.28 and 0.2.2.x before 0.2.2.20-alpha allows remote attackers to cause a denial of service (daemon crash) or possibly execute arbitrary code via unspecified vectors. | 10.0 |
| 2010-01-25 | CVE-2010-0385 | Information Exposure vulnerability in TOR Tor before 0.2.1.22, and 0.2.2.x before 0.2.2.7-alpha, when functioning as a bridge directory authority, allows remote attackers to obtain sensitive information about bridge identities and bridge descriptors via a dbg-stability.txt directory query. | 5.0 |
| 2010-01-25 | CVE-2010-0383 | Information Exposure vulnerability in TOR Tor before 0.2.1.22, and 0.2.2.x before 0.2.2.7-alpha, uses deprecated identity keys for certain directory authorities, which makes it easier for man-in-the-middle attackers to compromise the anonymity of traffic sources and destinations. | 5.0 |
| 2009-07-10 | CVE-2009-2426 | Remote Security vulnerability in Tor The connection_edge_process_relay_cell_not_open function in src/or/relay.c in Tor 0.2.x before 0.2.0.35 and 0.1.x before 0.1.2.8-beta allows exit relays to have an unspecified impact by causing controllers to accept DNS responses that redirect to an internal IP address via unknown vectors. | 5.0 |
| 2009-02-03 | CVE-2009-0414 | Resource Management Errors vulnerability in TOR Unspecified vulnerability in Tor before 0.2.0.33 has unspecified impact and remote attack vectors that trigger heap corruption. | 10.0 |
| 2008-12-09 | CVE-2008-5398 | Permissions, Privileges, and Access Controls vulnerability in TOR Tor before 0.2.0.32 does not properly process the ClientDNSRejectInternalAddresses configuration option in situations where an exit relay issues a policy-based refusal of a stream, which allows remote exit relays to have an unknown impact by mapping an internal IP address to the destination hostname of a refused stream. | 9.3 |
| 2008-12-09 | CVE-2008-5397 | Permissions, Privileges, and Access Controls vulnerability in TOR Tor before 0.2.0.32 does not properly process the (1) User and (2) Group configuration options, which might allow local users to gain privileges by leveraging unintended supplementary group memberships of the Tor process. | 7.2 |
| 2006-07-07 | CVE-2006-3419 | Remote Security vulnerability in Tor Tor before 0.1.1.20 uses OpenSSL pseudo-random bytes (RAND_pseudo_bytes) instead of cryptographically strong RAND_bytes, and seeds the entropy value at start-up with 160-bit chunks without reseeding, which makes it easier for attackers to conduct brute force guessing attacks. | 5.0 |
| 2006-07-07 | CVE-2006-3418 | Remote Security vulnerability in Tor Tor before 0.1.1.20 does not validate that a server descriptor's fingerprint line matches its identity key, which allows remote attackers to spoof the fingerprint line, which might be trusted by users or other applications. | 5.0 |
| 2006-07-07 | CVE-2006-3417 | Remote Security vulnerability in Tor Tor client before 0.1.1.20 prefers entry points based on is_fast or is_stable flags, which could allow remote attackers to be preferred over nodes that are identified as more trustworthy "entry guard" (is_guard) systems by directory authorities. | 6.4 |