Tor Project 関連製品全体の CVE とセキュリティ脆弱性情報を集約し、CVSS、EPSS、公開日、脆弱性情報データを掲載しています。
過去の問題は主に パス処理の欠陥 and バッファオーバーフロー などに関し、一部は vendor impact memory corruption を招き、vendor surface software deployment and vendor surface production workloads 関連の場面に影響します。
掲載データは公開脆弱性情報とセキュリティ公告に基づき、過去の暴露面と修補優先度の評価に利用できます。
| CVE | 概要 | ソース | CVSS 最大値 | EPSS（%） | 公開 | 更新 |
|---|---|---|---|---|---|---|
| CVE-2012-3519 | routerlist.c in Tor before 0.2.2.38 uses a different amount of time for relay-list iteration depending on which relay is chosen, which might allow remote attackers to obtain sensitive information about relay selection via a timing side-channel attack. | [email protected] | 5.0 | 2.42% | 2012-08-25 | 2026-06-16 |
| CVE-2012-3518 | 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. | [email protected] | 5.0 | 2.77% | 2012-08-25 | 2026-06-16 |
| CVE-2012-3517 | 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. | [email protected] | 5.0 | 2.77% | 2012-08-25 | 2026-06-16 |
| CVE-2011-4897 | 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. | [email protected] | 4.3 | 1.62% | 2011-12-22 | 2026-06-16 |
| CVE-2011-4896 | 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. | [email protected] | 4.3 | 1.59% | 2011-12-22 | 2026-06-16 |
| CVE-2011-4895 | 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. | [email protected] | 4.3 | 1.62% | 2011-12-22 | 2026-06-16 |
| CVE-2011-4894 | 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. | [email protected] | 4.3 | 1.62% | 2011-12-22 | 2026-06-16 |
| CVE-2011-2778 | 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. | [email protected] | 7.6 | 3.82% | 2011-12-22 | 2026-06-16 |
| CVE-2011-2769 | 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. | [email protected] | 4.3 | 1.20% | 2011-12-22 | 2026-06-16 |
| CVE-2011-2768 | 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. | [email protected] | 5.8 | 0.77% | 2011-12-22 | 2026-06-16 |
| CVE-2011-1924 | 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. | [email protected] | 5.0 | 2.82% | 2011-06-14 | 2026-06-16 |
| CVE-2011-0493 | Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha might allow remote attackers to cause a denial of service (assertion failure and daemon exit) via vectors related to malformed router caches and improper handling of integer values. | [email protected] | 5.0 | 2.52% | 2011-01-19 | 2026-06-16 |
| CVE-2011-0492 | 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 (assertion failure and daemon exit) via blobs that trigger a certain file size, as demonstrated by the cached-descriptors.new file. | [email protected] | 5.0 | 2.52% | 2011-01-19 | 2026-06-16 |
| CVE-2011-0491 | 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." | [email protected] | 5.0 | 2.52% | 2011-01-19 | 2026-06-16 |
| CVE-2011-0490 | 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. | [email protected] | 5.0 | 2.52% | 2011-01-19 | 2026-06-16 |
| CVE-2011-0427 | 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. | [email protected] | 6.8 | 4.44% | 2011-01-19 | 2026-06-16 |
| CVE-2011-0016 | 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. | [email protected] | 2.1 | 0.40% | 2011-01-19 | 2026-06-16 |
| CVE-2011-0015 | 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. | [email protected] | 5.0 | 3.10% | 2011-01-19 | 2026-06-16 |
| CVE-2010-1676 | 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. | [email protected] | 10.0 | 7.88% | 2010-12-21 | 2026-06-16 |
| CVE-2010-0385 | 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. | [email protected] | 5.0 | 1.96% | 2010-01-25 | 2026-06-16 |