Filtered by vendor Tor
Subscribe
Total
57 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2012-3517 | 1 Tor | 1 Tor | 2013-08-21 | 5.0 MEDIUM | N/A |
| Use-after-free vulnerability in dns.c in Tor before 0.2.2.38 might allow remote attackers to cause a denial of service (daemon crash) via vectors related to failed DNS requests. | |||||
| CVE-2012-3518 | 1 Tor | 1 Tor | 2013-08-21 | 5.0 MEDIUM | N/A |
| The networkstatus_parse_vote_from_string function in routerparse.c in Tor before 0.2.2.38 does not properly handle an invalid flavor name, which allows remote attackers to cause a denial of service (out-of-bounds read and daemon crash) via a crafted (1) vote document or (2) consensus document. | |||||
| CVE-2011-2769 | 1 Tor | 1 Tor | 2012-01-18 | 4.3 MEDIUM | N/A |
| 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. | |||||
| CVE-2011-2778 | 1 Tor | 1 Tor | 2012-01-18 | 7.6 HIGH | N/A |
| 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. | |||||
| CVE-2011-2768 | 1 Tor | 1 Tor | 2012-01-18 | 5.8 MEDIUM | N/A |
| 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. | |||||
| CVE-2011-4896 | 1 Tor | 1 Tor | 2011-12-29 | 4.3 MEDIUM | N/A |
| 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. | |||||
| CVE-2011-4897 | 1 Tor | 1 Tor | 2011-12-29 | 4.3 MEDIUM | N/A |
| 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. | |||||
| CVE-2011-4895 | 1 Tor | 1 Tor | 2011-12-22 | 4.3 MEDIUM | N/A |
| 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. | |||||
| CVE-2011-4894 | 1 Tor | 1 Tor | 2011-12-22 | 4.3 MEDIUM | N/A |
| 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. | |||||
| CVE-2011-0015 | 1 Tor | 1 Tor | 2011-07-18 | 5.0 MEDIUM | N/A |
| 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. | |||||
| CVE-2011-1924 | 1 Tor | 1 Tor | 2011-06-29 | 5.0 MEDIUM | N/A |
| 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. | |||||
| CVE-2010-0384 | 1 Tor | 1 Tor | 2011-04-26 | 2.1 LOW | N/A |
| Tor 0.2.2.x before 0.2.2.7-alpha, when functioning as a directory mirror, does not prevent logging of the client IP address upon detection of erroneous client behavior, which might make it easier for local users to discover the identities of clients in opportunistic circumstances by reading log files. | |||||
| CVE-2009-0414 | 1 Tor | 1 Tor | 2011-03-07 | 10.0 HIGH | N/A |
| Unspecified vulnerability in Tor before 0.2.0.33 has unspecified impact and remote attack vectors that trigger heap corruption. | |||||
| CVE-2007-4096 | 1 Tor | 1 Tor | 2011-03-07 | 5.8 MEDIUM | N/A |
| 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-4098 | 1 Tor | 1 Tor | 2011-03-07 | 5.8 MEDIUM | N/A |
| 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 | 1 Tor | 1 Tor | 2011-03-07 | 5.8 MEDIUM | N/A |
| 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-4097 | 1 Tor | 1 Tor | 2011-03-07 | 6.4 MEDIUM | N/A |
| 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-3165 | 1 Tor | 1 Tor | 2011-03-07 | 5.0 MEDIUM | N/A |
| 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-2010-1676 | 1 Tor | 1 Tor | 2011-01-21 | 10.0 HIGH | N/A |
| 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. | |||||
| CVE-2011-0016 | 1 Tor | 1 Tor | 2011-01-21 | 2.1 LOW | N/A |
| 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. | |||||