Tor
by Tor
Source repositories
CVEs (89)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2009-0936 | 0.00 | — | 0.02 | Mar 18, 2009 | Unspecified vulnerability in Tor before 0.2.0.34 allows attackers to cause a denial of service (infinite loop) via "corrupt votes." | |||
| CVE-2009-0654 | 0.00 | — | 0.02 | Feb 20, 2009 | 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,… | |||
| CVE-2009-0414 | 0.00 | — | 0.03 | Feb 3, 2009 | Unspecified vulnerability in Tor before 0.2.0.33 has unspecified impact and remote attack vectors that trigger heap corruption. | |||
| CVE-2008-5398 | 0.00 | — | 0.02 | Dec 9, 2008 | 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… | |||
| CVE-2008-5397 | 0.00 | — | 0.00 | Dec 9, 2008 | 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. | |||
| CVE-2007-4096 | 0.00 | — | 0.02 | Jul 30, 2007 | Buffer overflow in Tor before 0.1.2.15, when using BSD natd support, allows remote attackers to cause a denial of service via unspecified vectors. | |||
| CVE-2007-4097 | 0.00 | — | 0.02 | Jul 30, 2007 | Tor before 0.1.2.15 sends "destroy cells" containing the reason for tearing down a circuit, which allows remote attackers to obtain sensitive information, contrary to specifications. | |||
| CVE-2007-4098 | 0.00 | — | 0.02 | Jul 30, 2007 | Tor before 0.1.2.15 does not properly distinguish "streamids from different exits," which might allow remote attackers with control over Tor routers to inject cells into arbitrary streams. | |||
| CVE-2007-4099 | 0.00 | — | 0.02 | Jul 30, 2007 | Tor before 0.1.2.15 can select a guard node beyond the first listed never-before-connected-to guard node, which allows remote attackers with control of certain guard nodes to obtain sensitive information and possibly leverage further attacks. | |||
| CVE-2007-3165 | 0.00 | — | 0.01 | Jun 11, 2007 | Tor before 0.1.2.14 can construct circuits in which an entry guard is in the same family as the exit node, which might compromise the anonymity of traffic sources and destinations by exposing traffic to inappropriate remote observers. | |||
| CVE-2007-1103 | 0.00 | — | 0.02 | Feb 26, 2007 | Tor does not verify a node's uptime and bandwidth advertisements, which allows remote attackers who operate a low resource node to make false claims of greater resources, which places the node into use for many circuits and compromises the anonymity of traffic sources and… | |||
| CVE-2006-6893 | 0.00 | — | 0.02 | Dec 31, 2006 | Tor allows remote attackers to discover the IP address of a hidden service by accessing this service at a high rate, thereby changing the server's CPU temperature and consequently changing the pattern of time values visible through (1) ICMP timestamps, (2) TCP sequence numbers,… | |||
| CVE-2006-4508 | 0.00 | — | 0.02 | Aug 31, 2006 | Unspecified vulnerability in (1) Tor 0.1.0.x before 0.1.0.18 and 0.1.1.x before 0.1.1.23, and (2) ScatterChat before 1.0.2, allows remote attackers operating a Tor entry node to route arbitrary Tor traffic through clients or cause a denial of service (flood) via unspecified… | |||
| CVE-2006-3409 | 0.00 | — | 0.04 | Jul 7, 2006 | Integer overflow in Tor before 0.1.1.20 allows remote attackers to execute arbitrary code via crafted large inputs, which result in a buffer overflow when elements are added to smartlists. | |||
| CVE-2006-3418 | 0.00 | — | 0.02 | Jul 7, 2006 | 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. | |||
| CVE-2006-3419 | 0.00 | — | 0.02 | Jul 7, 2006 | 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. | |||
| CVE-2006-3411 | 0.00 | — | 0.01 | Jul 7, 2006 | TLS handshakes in Tor before 0.1.1.20 generate public-private keys based on TLS context rather than the connection, which makes it easier for remote attackers to conduct brute force attacks on the encryption keys. | |||
| CVE-2006-3412 | 0.00 | — | 0.02 | Jul 7, 2006 | Tor before 0.1.1.20 does not sufficiently obey certain firewall options, which allows remote attackers to bypass intended access restrictions for dirservers, direct connections, or proxy servers. | |||
| CVE-2006-3417 | 0.00 | — | 0.02 | Jul 7, 2006 | 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. | |||
| CVE-2006-3415 | 0.00 | — | 0.02 | Jul 7, 2006 | Tor before 0.1.1.20 uses improper logic to validate the "OR" destination, which allows remote attackers to perform a man-in-the-middle (MITM) attack via unspecified vectors. |
- CVE-2009-0936Mar 18, 2009risk 0.00cvss —epss 0.02
Unspecified vulnerability in Tor before 0.2.0.34 allows attackers to cause a denial of service (infinite loop) via "corrupt votes."
- CVE-2009-0654Feb 20, 2009risk 0.00cvss —epss 0.02
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,…
- CVE-2009-0414Feb 3, 2009risk 0.00cvss —epss 0.03
Unspecified vulnerability in Tor before 0.2.0.33 has unspecified impact and remote attack vectors that trigger heap corruption.
- CVE-2008-5398Dec 9, 2008risk 0.00cvss —epss 0.02
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…
- CVE-2008-5397Dec 9, 2008risk 0.00cvss —epss 0.00
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.
- CVE-2007-4096Jul 30, 2007risk 0.00cvss —epss 0.02
Buffer overflow in Tor before 0.1.2.15, when using BSD natd support, allows remote attackers to cause a denial of service via unspecified vectors.
- CVE-2007-4097Jul 30, 2007risk 0.00cvss —epss 0.02
Tor before 0.1.2.15 sends "destroy cells" containing the reason for tearing down a circuit, which allows remote attackers to obtain sensitive information, contrary to specifications.
- CVE-2007-4098Jul 30, 2007risk 0.00cvss —epss 0.02
Tor before 0.1.2.15 does not properly distinguish "streamids from different exits," which might allow remote attackers with control over Tor routers to inject cells into arbitrary streams.
- CVE-2007-4099Jul 30, 2007risk 0.00cvss —epss 0.02
Tor before 0.1.2.15 can select a guard node beyond the first listed never-before-connected-to guard node, which allows remote attackers with control of certain guard nodes to obtain sensitive information and possibly leverage further attacks.
- CVE-2007-3165Jun 11, 2007risk 0.00cvss —epss 0.01
Tor before 0.1.2.14 can construct circuits in which an entry guard is in the same family as the exit node, which might compromise the anonymity of traffic sources and destinations by exposing traffic to inappropriate remote observers.
- CVE-2007-1103Feb 26, 2007risk 0.00cvss —epss 0.02
Tor does not verify a node's uptime and bandwidth advertisements, which allows remote attackers who operate a low resource node to make false claims of greater resources, which places the node into use for many circuits and compromises the anonymity of traffic sources and…
- CVE-2006-6893Dec 31, 2006risk 0.00cvss —epss 0.02
Tor allows remote attackers to discover the IP address of a hidden service by accessing this service at a high rate, thereby changing the server's CPU temperature and consequently changing the pattern of time values visible through (1) ICMP timestamps, (2) TCP sequence numbers,…
- CVE-2006-4508Aug 31, 2006risk 0.00cvss —epss 0.02
Unspecified vulnerability in (1) Tor 0.1.0.x before 0.1.0.18 and 0.1.1.x before 0.1.1.23, and (2) ScatterChat before 1.0.2, allows remote attackers operating a Tor entry node to route arbitrary Tor traffic through clients or cause a denial of service (flood) via unspecified…
- CVE-2006-3409Jul 7, 2006risk 0.00cvss —epss 0.04
Integer overflow in Tor before 0.1.1.20 allows remote attackers to execute arbitrary code via crafted large inputs, which result in a buffer overflow when elements are added to smartlists.
- CVE-2006-3418Jul 7, 2006risk 0.00cvss —epss 0.02
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.
- CVE-2006-3419Jul 7, 2006risk 0.00cvss —epss 0.02
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.
- CVE-2006-3411Jul 7, 2006risk 0.00cvss —epss 0.01
TLS handshakes in Tor before 0.1.1.20 generate public-private keys based on TLS context rather than the connection, which makes it easier for remote attackers to conduct brute force attacks on the encryption keys.
- CVE-2006-3412Jul 7, 2006risk 0.00cvss —epss 0.02
Tor before 0.1.1.20 does not sufficiently obey certain firewall options, which allows remote attackers to bypass intended access restrictions for dirservers, direct connections, or proxy servers.
- CVE-2006-3417Jul 7, 2006risk 0.00cvss —epss 0.02
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.
- CVE-2006-3415Jul 7, 2006risk 0.00cvss —epss 0.02
Tor before 0.1.1.20 uses improper logic to validate the "OR" destination, which allows remote attackers to perform a man-in-the-middle (MITM) attack via unspecified vectors.
Page 4 of 5