Debian Tor vulnerabilities

CVE-2012-5573 [MEDIUM] CVE-2012-5573: tor - The connection_edge_process_relay_cell function in or/relay.c in Tor before 0.2.... The connection_edge_process_relay_cell function in or/relay.c in Tor before 0.2.3.25 maintains circuits even if an unexpected SENDME cell arrives, which might allow remote attackers to cause a denial of service (memory consumption or excessive cell reception rate) or bypass intended flow-control restrictions via a RELAY_COMMAND_SENDME command. Scope: local bookworm: res

CVE-2012-2249 [MEDIUM] CVE-2012-2249: tor - Tor before 0.2.3.23-rc allows remote attackers to cause a denial of service (ass... Tor before 0.2.3.23-rc allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a renegotiation attempt that occurs after the initiation of the V3 link protocol. Scope: local bookworm: resolved (fixed in 0.2.3.23-rc-1) bullseye: resolved (fixed in 0.2.3.23-rc-1) forky: resolved (fixed in 0.2.3.23-rc-1) sid: resolved (fixed in 0.2.3.23

CVE-2011-2778 [HIGH] CVE-2011-2778: tor - Multiple heap-based buffer overflows in Tor before 0.2.2.35 allow remote attacke... 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. Scope: local bookworm: resolved (fixed in 0.2.2.35-1) bullseye: resolved (fixed in 0.2.2.35-1) forky: resolv

CVE-2011-0490 [MEDIUM] CVE-2011-0490: tor - Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha makes calls to Libevent wi... 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. Scope: local bookworm: resolved (fixed in 0.2.1.29-1) bullseye: resolved (fixed in 0.2.1.29-1) forky: resolved (fixed in 0.2.1.29-1) sid:

CVE-2011-0493 [MEDIUM] CVE-2011-0493: tor - Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha might allow remote attacke... 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. Scope: local bookworm: resolved (fixed in 0.2.1.29-1) bullseye: resolved (fixed in 0.2.1.29-1) forky: resolved (fixed in 0.2.1.29-1) sid

CVE-2011-0492 [MEDIUM] CVE-2011-0492: tor - Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha allows remote attackers to... 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. Scope: local bookworm: resolved (fixed in 0.2.1.29-1) bullseye: resolved (fixed in 0.2.1.29-1) forky: resolved (fixed in 0.2.1.29-1)

CVE-2011-1924 [MEDIUM] CVE-2011-1924: tor - Buffer overflow in the policy_summarize function in or/policies.c in Tor before ... 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. Scope: local bookworm: resolved (fixed in 0.2.1.30-1) bullseye: resolved (fixed in 0.2.1.30-1) forky: resolved (fixed in 0.2.1.30-1) sid:

CVE-2011-0015 [MEDIUM] CVE-2011-0015: tor - Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha does not properly check th... 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. Scope: local bookworm: resolved (fixed in 0.2.1.29-1) bullseye: resolved (fixed in 0.2.1.29-1) forky: resolved (fixed in 0.2.1.29-1) sid: resolved (fixe

CVE-2011-2769 [MEDIUM] CVE-2011-2769: tor - Tor before 0.2.2.34, when configured as a bridge, accepts the CREATE and CREATE_... 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. Scope: local bookworm: resolved (fixed in 0.2.2.34-1) bullseye: resolved (fixed in 0.2.2.34-1) forky: resolved (fixed in 0.2.2.34-1) si

CVE-2011-2768 [MEDIUM] CVE-2011-2768: tor - Tor before 0.2.2.34, when configured as a client or bridge, sends a TLS certific... 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. Scope: local bookworm: resolved (fixed in 0.2.2.34-1) bullseye: resolv

CVE-2011-0491 [MEDIUM] CVE-2011-0491: tor - The tor_realloc function in Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alph... 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." Scope: local bookworm: resolved (fixed in 0.2.1.29-1) bullseye: resolved (fixed in 0.2.1.2

CVE-2011-0427 [MEDIUM] CVE-2011-0427: tor - Heap-based buffer overflow in Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-al... 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. Scope: local bookworm: resolved (fixed in 0.2.1.29-1) bullseye: resolved (fixed in 0.2.1.29-1) forky: resolved (fixed in 0.2.1.29-1)

CVE-2011-4895 [MEDIUM] CVE-2011-4895: tor - Tor before 0.2.2.34, when configured as a bridge, sets up circuits through a pro... 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. Scope: local bookworm: resolved (fixed in 0.2.2.34-1) bullseye: resolved (fixed in 0.2.2.34-1) forky: resolved (fixed in 0.2.2.34-1) sid: resolved

CVE-2011-0016 [LOW] CVE-2011-0016: tor - Tor before 0.2.1.29 and 0.2.2.x before 0.2.2.21-alpha does not properly manage k... 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. Scope: local bookworm: resolved (fixed in 0.2.1.29-1) bullseye: resolved (fixed in 0.2.1.29-1) forky: resolved (fixed in 0.2

CVE-2011-4896 [MEDIUM] CVE-2011-4896: tor - Tor before 0.2.2.24-alpha continues to use a reachable bridge that was previousl... 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. Scope: local bookworm: resolved (fixed in 0.2.2.27-beta-1) bullseye: resolved (fixed

CVE-2011-4897 [MEDIUM] CVE-2011-4897: tor - Tor before 0.2.2.25-alpha, when configured as a relay without the Nickname confi... 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. Scope: local bookworm: resolved (fixed in 0.2.2.27-beta-1) bullseye: resolved (fixed in 0.2.2.27-beta-1) forky: resolved (fixed in

CVE-2011-4894 [MEDIUM] CVE-2011-4894: tor - Tor before 0.2.2.34, when configured as a bridge, uses direct DirPort access ins... 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. Scope: local bookworm: resolved (fixed in 0.2.2.34-1) bullseye: resolved (fixed in 0.2.2.34-1) forky: resolved (fixed in 0.2.2.34-1) sid: reso

CVE-2010-1676 [CRITICAL] CVE-2010-1676: tor - Heap-based buffer overflow in Tor before 0.2.1.28 and 0.2.2.x before 0.2.2.20-al... 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. Scope: local bookworm: resolved (fixed in 0.2.1.26-6) bullseye: resolved (fixed in 0.2.1.26-6) forky: resolved (fixed in 0.2.1.26-6) sid: resolved (fixed in 0

CVE-2010-0383 [MEDIUM] CVE-2010-0383: tor - Tor before 0.2.1.22, and 0.2.2.x before 0.2.2.7-alpha, uses deprecated identity ... Tor before 0.2.1.22, and 0.2.2.x before 0.2.2.7-alpha, uses deprecated identity keys for certain directory authorities, which makes it easier for man-in-the-middle attackers to compromise the anonymity of traffic sources and destinations. Scope: local bookworm: resolved (fixed in 0.2.1.22-1) bullseye: resolved (fixed in 0.2.1.22-1) forky: resolved (fixed in 0.2.1.22-1)

CVE-2010-0384 [LOW] CVE-2010-0384: tor - Tor 0.2.2.x before 0.2.2.7-alpha, when functioning as a directory mirror, does n... 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. Scope: local bookworm: resolved bullseye: resolved forky: resolved sid: