Filtered by vendor Torproject
Subscribe
Total
40 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2020-10593 | 2 Opensuse, Torproject | 3 Backports Sle, Leap, Tor | 2023-02-03 | 5.0 MEDIUM | 7.5 HIGH |
Tor before 0.3.5.10, 0.4.x before 0.4.1.9, and 0.4.2.x before 0.4.2.7 allows remote attackers to cause a Denial of Service (memory leak), aka TROVE-2020-004. This occurs in circpad_setup_machine_on_circ because a circuit-padding machine can be negotiated twice on the same circuit. | |||||
CVE-2023-23589 | 3 Debian, Fedoraproject, Torproject | 3 Debian Linux, Fedora, Tor | 2023-01-30 | N/A | 6.5 MEDIUM |
The SafeSocks option in Tor before 0.4.7.13 has a logic error in which the unsafe SOCKS4 protocol can be used but not the safe SOCKS4a protocol, aka TROVE-2022-002. | |||||
CVE-2022-33903 | 1 Torproject | 1 Tor | 2022-07-25 | N/A | 7.5 HIGH |
Tor 0.4.7.x before 0.4.7.8 allows a denial of service via the wedging of RTT estimation. | |||||
CVE-2021-34549 | 1 Torproject | 1 Tor | 2022-07-12 | 5.0 MEDIUM | 7.5 HIGH |
An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-005. Hashing is mishandled for certain retrieval of circuit data. Consequently. an attacker can trigger the use of an attacker-chosen circuit ID to cause algorithm inefficiency. | |||||
CVE-2021-28090 | 2 Fedoraproject, Torproject | 2 Fedora, Tor | 2022-05-16 | 5.0 MEDIUM | 5.3 MEDIUM |
Tor before 0.4.5.7 allows a remote attacker to cause Tor directory authorities to exit with an assertion failure, aka TROVE-2021-002. | |||||
CVE-2021-28089 | 2 Fedoraproject, Torproject | 2 Fedora, Tor | 2022-05-16 | 5.0 MEDIUM | 7.5 HIGH |
Tor before 0.4.5.7 allows a remote participant in the Tor directory protocol to exhaust CPU resources on a target, aka TROVE-2021-001. | |||||
CVE-2017-16541 | 5 Apple, Debian, Linux and 2 more | 10 Macos, Debian Linux, Linux Kernel and 7 more | 2022-04-18 | 4.3 MEDIUM | 6.5 MEDIUM |
Tor Browser before 7.0.9 on macOS and Linux allows remote attackers to bypass the intended anonymity feature and discover a client IP address via vectors involving a crafted web site that leverages file:// mishandling in Firefox, aka TorMoil. NOTE: Tails is unaffected. | |||||
CVE-2020-8516 | 1 Torproject | 1 Tor | 2022-04-18 | 5.0 MEDIUM | 5.3 MEDIUM |
** DISPUTED ** The daemon in Tor through 0.4.1.8 and 0.4.2.x through 0.4.2.6 does not verify that a rendezvous node is known before attempting to connect to it, which might make it easier for remote attackers to discover circuit information. NOTE: The network team of Tor claims this is an intended behavior and not a vulnerability. | |||||
CVE-2021-46702 | 2 Microsoft, Torproject | 2 Windows, Tor | 2022-03-10 | 2.1 LOW | 5.5 MEDIUM |
Tor Browser 9.0.7 on Windows 10 build 10586 is vulnerable to information disclosure. This could allow local attackers to bypass the intended anonymity feature and obtain information regarding the onion services visited by a local user. This can be accomplished by analyzing RAM memory even several hours after the local user used the product. This occurs because the product doesn't properly free memory. | |||||
CVE-2020-10592 | 2 Opensuse, Torproject | 3 Backports, Leap, Tor | 2022-01-01 | 7.8 HIGH | 7.5 HIGH |
Tor before 0.3.5.10, 0.4.x before 0.4.1.9, and 0.4.2.x before 0.4.2.7 allows remote attackers to cause a Denial of Service (CPU consumption), aka TROVE-2020-002. | |||||
CVE-2021-39246 | 4 Apple, Linux, Microsoft and 1 more | 4 Macos, Linux Kernel, Windows and 1 more | 2021-10-01 | 3.6 LOW | 6.1 MEDIUM |
Tor Browser through 10.5.6 and 11.x through 11.0a4 allows a correlation attack that can compromise the privacy of visits to v2 onion addresses. Exact timestamps of these onion-service visits are logged locally, and an attacker might be able to compare them to timestamp data collected by the destination server (or collected by a rogue site within the Tor network). | |||||
CVE-2021-34550 | 1 Torproject | 1 Tor | 2021-09-20 | 5.0 MEDIUM | 7.5 HIGH |
An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-006. The v3 onion service descriptor parsing allows out-of-bounds memory access, and a client crash, via a crafted onion service descriptor | |||||
CVE-2021-34548 | 1 Torproject | 1 Tor | 2021-09-14 | 5.0 MEDIUM | 7.5 HIGH |
An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-003. An attacker can forge RELAY_END or RELAY_RESOLVED to bypass the intended access control for ending a stream. | |||||
CVE-2021-38385 | 1 Torproject | 1 Tor | 2021-09-01 | 5.0 MEDIUM | 7.5 HIGH |
Tor before 0.3.5.16, 0.4.5.10, and 0.4.6.7 mishandles the relationship between batch-signature verification and single-signature verification, leading to a remote assertion failure, aka TROVE-2021-007. | |||||
CVE-2020-15572 | 1 Torproject | 1 Tor | 2021-07-21 | 4.3 MEDIUM | 7.5 HIGH |
Tor before 0.4.3.6 has an out-of-bounds memory access that allows a remote denial-of-service (crash) attack against Tor instances built to use Mozilla Network Security Services (NSS), aka TROVE-2020-001. | |||||
CVE-2019-12383 | 1 Torproject | 1 Tor Browser | 2020-08-24 | 4.3 MEDIUM | 4.3 MEDIUM |
Tor Browser before 8.0.1 has an information exposure vulnerability. It allows remote attackers to detect the browser's UI locale by measuring a button width, even if the user has a "Don't send my language" setting. | |||||
CVE-2019-8955 | 1 Torproject | 1 Tor | 2020-08-24 | 5.0 MEDIUM | 7.5 HIGH |
In Tor before 0.3.3.12, 0.3.4.x before 0.3.4.11, 0.3.5.x before 0.3.5.8, and 0.4.x before 0.4.0.2-alpha, remote denial of service against Tor clients and relays can occur via memory exhaustion in the KIST cell scheduler. | |||||
CVE-2015-2929 | 1 Torproject | 1 Tor | 2020-02-01 | 5.0 MEDIUM | 7.5 HIGH |
The Hidden Service (HS) client implementation in Tor before 0.2.4.27, 0.2.5.x before 0.2.5.12, and 0.2.6.x before 0.2.6.7 allows remote servers to cause a denial of service (assertion failure and application exit) via a malformed HS descriptor. | |||||
CVE-2015-2928 | 1 Torproject | 1 Tor | 2020-02-01 | 5.0 MEDIUM | 7.5 HIGH |
The Hidden Service (HS) server implementation in Tor before 0.2.4.27, 0.2.5.x before 0.2.5.12, and 0.2.6.x before 0.2.6.7 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via unspecified vectors. | |||||
CVE-2015-2689 | 1 Torproject | 1 Tor | 2020-01-31 | 5.0 MEDIUM | 7.5 HIGH |
Tor before 0.2.4.26 and 0.2.5.x before 0.2.5.11 does not properly handle pending-connection resolve states during periods of high DNS load, which allows remote attackers to cause a denial of service (assertion failure and daemon exit) via crafted packets. |