Vulnerabilities > TOR > TOR > 0.1.1.1
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2011-01-19 | CVE-2011-0491 | Improper Input Validation vulnerability in TOR The tor_realloc function in Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha does not validate a certain size value during memory allocation, which might allow remote attackers to cause a denial of service (daemon crash) via unspecified vectors, related to "underflow errors." | 5.0 |
2011-01-19 | CVE-2011-0490 | Denial of Service vulnerability in Tor Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha makes calls to Libevent within Libevent log handlers, which might allow remote attackers to cause a denial of service (daemon crash) via vectors that trigger certain log messages. | 5.0 |
2011-01-19 | CVE-2011-0427 | Improper Restriction of Operations Within the Bounds of A Memory Buffer vulnerability in TOR Heap-based buffer overflow in 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 (memory corruption and application crash) or possibly execute arbitrary code via unspecified vectors. | 6.8 |
2011-01-19 | CVE-2011-0016 | Resource Management Errors vulnerability in TOR Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha does not properly manage key data in memory, which might allow local users to obtain sensitive information by leveraging the ability to read memory that was previously used by a different process. | 2.1 |
2011-01-19 | CVE-2011-0015 | Improper Input Validation vulnerability in TOR Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha does not properly check the amount of compression in zlib-compressed data, which allows remote attackers to cause a denial of service via a large compression factor. | 5.0 |
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 |