0.2.0.34 Alpha : Security Vulnerabilities

Cpe Name:cpe:/a:tor:tor:0.2.0.34:alpha

CVSS Scores Greater Than: 0 1 2 3 4 5 6 7 8 9

Sort Results By : Cve Number Descending Cve Number Ascending CVSS Score Descending Number Of Exploits Descending

Copy Results Download Results Select Table

#	CVE ID	CWE ID	Vulnerability Type(s)	Publish Date	Update Date	Score	Gained Access Level	Access	Complexity	Authentication	Conf.	Integ.	Avail.
1	CVE-2011-4897	200	+Info	2011-12-22	2011-12-30	4.3	None	Remote	Medium	Not required	Partial	None	None
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.
2	CVE-2011-4896	200	+Info	2011-12-22	2011-12-30	4.3	None	Remote	Medium	Not required	Partial	None	None
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.
3	CVE-2011-4895	200	+Info	2011-12-22	2011-12-23	4.3	None	Remote	Medium	Not required	Partial	None	None
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.
4	CVE-2011-4894	200	+Info	2011-12-22	2011-12-23	4.3	None	Remote	Medium	Not required	Partial	None	None
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.
5	CVE-2011-2778	119	DoS Exec Code Overflow Mem. Corr.	2011-12-22	2012-01-18	7.6	None	Remote	High	Not required	Complete	Complete	Complete
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.
6	CVE-2011-2769	200	+Info	2011-12-22	2012-01-18	4.3	None	Remote	Medium	Not required	Partial	None	None
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.
7	CVE-2011-2768	264	Bypass	2011-12-22	2012-01-18	5.8	None	Remote	Medium	Not required	Partial	Partial	None
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.
8	CVE-2011-1924	119	DoS Overflow	2011-06-14	2011-06-30	5.0	None	Remote	Low	Not required	None	None	Partial
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.
9	CVE-2011-0493	189	DoS	2011-01-19	2011-02-01	5.0	None	Remote	Low	Not required	None	None	Partial
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.
10	CVE-2011-0492	399	DoS	2011-01-19	2011-02-01	5.0	None	Remote	Low	Not required	None	None	Partial
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.
11	CVE-2011-0491	20	DoS	2011-01-19	2011-02-12	5.0	None	Remote	Low	Not required	None	None	Partial
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."
12	CVE-2011-0490		DoS	2011-01-19	2011-02-12	5.0	None	Remote	Low	Not required	None	None	Partial
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.
13	CVE-2011-0427	119	DoS Exec Code Overflow Mem. Corr.	2011-01-19	2011-07-19	6.8	None	Remote	Medium	Not required	Partial	Partial	Partial
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.
14	CVE-2011-0016	399	+Info	2011-01-19	2011-01-22	2.1	None	Local	Low	Not required	Partial	None	None
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.
15	CVE-2011-0015	20	DoS	2011-01-19	2011-07-19	5.0	None	Remote	Low	Not required	None	None	Partial
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.
16	CVE-2009-2426			2009-07-10	2009-07-14	5.0	None	Remote	Low	Not required	None	None	Partial
The connection_edge_process_relay_cell_not_open function in src/or/relay.c in Tor 0.2.x before 0.2.0.35 and 0.1.x before 0.1.2.8-beta allows exit relays to have an unspecified impact by causing controllers to accept DNS responses that redirect to an internal IP address via unknown vectors. NOTE: some of these details are obtained from third party information.
17	CVE-2009-0654			2009-02-20	2009-02-25	5.1	None	Remote	High	Not required	Partial	Partial	Partial
Tor 0.2.0.28, and probably 0.2.0.34 and earlier, allows remote attackers, with control of an entry router and an exit router, to confirm that a sender and receiver are communicating via vectors involving (1) replaying, (2) modifying, (3) inserting, or (4) deleting a single cell, and then observing cell recognition errors at the exit router. NOTE: the vendor disputes the significance of this issue, noting that the product's design "accepted end-to-end correlation as an attack that is too expensive to solve."

Total number of vulnerabilities : 17 Page : 1 (This Page)