Torproject
Products by Torproject Sorted by Most Security Vulnerabilities since 2018
By the Year
In 2024 there have been 0 vulnerabilities in Torproject . Last year Torproject had 1 security vulnerability published. Right now, Torproject is on track to have less security vulnerabilities in 2024 than it did last year.
Year | Vulnerabilities | Average Score |
---|---|---|
2024 | 0 | 0.00 |
2023 | 1 | 6.50 |
2022 | 1 | 7.50 |
2021 | 6 | 7.13 |
2020 | 4 | 6.95 |
2019 | 3 | 5.70 |
2018 | 3 | 8.27 |
It may take a day or so for new Torproject vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Torproject Security Vulnerabilities
The SafeSocks option in Tor before 0.4.7.13 has a logic error in
CVE-2023-23589
6.5 - Medium
- January 14, 2023
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.
Tor 0.4.7.x before 0.4.7.8
CVE-2022-33903
7.5 - High
- July 17, 2022
Tor 0.4.7.x before 0.4.7.8 allows a denial of service via the wedging of RTT estimation.
Tor before 0.3.5.16
CVE-2021-38385
7.5 - High
- August 30, 2021
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.
assertion failure
An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-005
CVE-2021-34549
7.5 - High
- June 29, 2021
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.
Resource Exhaustion
An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-006
CVE-2021-34550
7.5 - High
- June 29, 2021
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
Buffer Overflow
An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-003
CVE-2021-34548
7.5 - High
- June 29, 2021
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.
Authentication Bypass by Spoofing
Tor before 0.4.5.7 allows a remote attacker to cause Tor directory authorities to exit with an assertion failure
CVE-2021-28090
5.3 - Medium
- March 19, 2021
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.
Tor before 0.4.5.7 allows a remote participant in the Tor directory protocol to exhaust CPU resources on a target
CVE-2021-28089
7.5 - High
- March 19, 2021
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.
Resource Exhaustion
Tor before 0.4.3.6 has an out-of-bounds memory access
CVE-2020-15572
7.5 - High
- July 15, 2020
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.
Buffer Overflow
Tor before 0.3.5.10, 0.4.x before 0.4.1.9, and 0.4.2.x before 0.4.2.7
CVE-2020-10593
7.5 - High
- March 23, 2020
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.
Memory Leak
Tor before 0.3.5.10, 0.4.x before 0.4.1.9, and 0.4.2.x before 0.4.2.7
CVE-2020-10592
7.5 - High
- March 23, 2020
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.
The daemon in Tor through 0.4.1.8 and 0.4.2.x through 0.4.2.6 does not verify
CVE-2020-8516
5.3 - Medium
- February 02, 2020
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
Tor Browser through 8.5.3 has an information exposure vulnerability
CVE-2019-13075
5.3 - Medium
- June 30, 2019
Tor Browser through 8.5.3 has an information exposure vulnerability. It allows remote attackers to detect the browser's language via vectors involving an IFRAME element, because text in that language is included in the title attribute of a LINK element for a non-HTML page. This is related to a behavior of Firefox before 68.
Information Disclosure
Tor Browser before 8.0.1 has an information exposure vulnerability
CVE-2019-12383
4.3 - Medium
- May 28, 2019
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.
Side Channel Attack
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
CVE-2019-8955
7.5 - High
- February 21, 2019
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.
Allocation of Resources Without Limits or Throttling
NoScript Classic before 5.1.8.7, as used in Tor Browser 7.x and other products
CVE-2018-16983
9.8 - Critical
- September 13, 2018
NoScript Classic before 5.1.8.7, as used in Tor Browser 7.x and other products, allows attackers to bypass script blocking via the text/html;/json Content-Type value.
An issue was discovered in Tor before 0.2.9.15, 0.3.1.x before 0.3.1.10, and 0.3.2.x before 0.3.2.10
CVE-2018-0490
7.5 - High
- March 05, 2018
An issue was discovered in Tor before 0.2.9.15, 0.3.1.x before 0.3.1.10, and 0.3.2.x before 0.3.2.10. The directory-authority protocol-list subprotocol implementation allows remote attackers to cause a denial of service (NULL pointer dereference and directory-authority crash) via a misformatted relay descriptor that is mishandled during voting.
NULL Pointer Dereference
A use-after-free issue was discovered in Tor 0.3.2.x before 0.3.2.10
CVE-2018-0491
7.5 - High
- March 05, 2018
A use-after-free issue was discovered in Tor 0.3.2.x before 0.3.2.10. It allows remote attackers to cause a denial of service (relay crash) because the KIST implementation allows a channel to be added more than once in the pending list.
Dangling pointer