CVE-2006-3408

CVE-2006-3408 affects the Tor project (dirserver) prior to 0.1.1.20, enabling remote denial of service via unknown vectors. The vulnerability details are described as unspecified; the impact is partial availability. A remediation is to upgrade to Tor 0.1.1.20 or later (as indicated in the descrip...

CVE-2006-3409

The CVE-2006-3409 entry concerns Tor before 0.1.1.20, where an integer overflow occurs when large inputs are added to smartlists, enabling potential remote code execution via crafted inputs. The affected component is Tor’s handling of smartlists; the root cause is the integer overflow. The provid...

CVE-2006-3411

CVE-2006-3411 relates to Tor prior to version 0.1.1.20, where TLS handshakes generate public–private keys based on TLS context rather than the specific connection. This design flaw can make it easier for remote attackers to perform brute-force attacks on the encryption keys. The vulnerability is ...

CVE-2006-3412

Tor prior to 0.1.1.20 does not sufficiently obey certain firewall options, allowing remote attackers to bypass intended access restrictions for dirservers, direct connections, or proxy servers. This is described across multiple connected sources (Red Hat, Ubuntu, OSV, NVD/NVD mirror). The affecte...

CVE-2006-3413

CVE-2006-3413 affects Privoxy when used with Tor prior to 0.1.1.20 on Apple macOS. The root cause is that the Privoxy configuration can log all data via the logfile, enabling exposure of potentially sensitive information. The Red Hat, Debian, Ubuntu, and OSV entries corroborate the same descripti...

CVE-2006-3414

CVE-2006-3414 affects Tor prior to 0.1.1.20. The issue arises in server descriptors that use hostnames instead of IP addresses, enabling remote attackers to influence/address selectivity by providing preferential address resolution and thereby arbitrarily grouping users. The available connected d...

CVE-2006-3416

CVE-2006-3416 affects Tor before 0.1.1.20. Affected component is the Tor relay handling logic where an unrecognized relay command kills the circuit, causing network circuits to be disbanded. The note from developers indicates this is a self‑DoS, not a fullstanding vulnerability, but multiple secu...

CVE-2006-3417

Tor client before 0.1.1.20 is vulnerable: the client may prefer directory entry points based on is_fast or is_stable flags instead of more trustworthy entry guards identified by authorities. Affected product: Tor client (pre-0.1.1.20). Root cause: selection bias in entry point ranking due to the ...

CVE-2006-3418

CVE-2006-3418 concerns Tor before 0.1.1.20, where the server descriptor fingerprint line is not validated against its identity key. This allows remote attackers to spoof the fingerprint line, which might be trusted by users or other applications. The connected documents corroborate the same descr...

CVE-2006-3419

CVE-2006-3419 affects Tor prior to 0.1.1.20. The issue stems from using OpenSSL RAND_pseudo_bytes instead of a cryptographically strong RAND_bytes, and seeding entropy at startup with 160-bit chunks without reseeding. This design makes brute-force guessing attacks more feasible for an attacker. M...

CVE-2006-3407: Undefined Security Weakness

Tor before 0.1.1.20 allows remote attackers to spoof log entries or possibly execute shell code via strings with non-printable characters...

CVE-2006-3408: Undefined Security Weakness

Unspecified vulnerability in the directory server dirserver in Tor before 0.1.1.20 allows remote attackers to cause an unspecified denial of service via unknown vectors...

CVE-2006-3414: Undefined Security Weakness

Tor before 0.1.1.20 supports server descriptors that contain hostnames instead of IP addresses, which allows remote attackers to arbitrarily group users by providing preferential address resolution...

CVE-2006-3410: Undefined Security Weakness

Tor before 0.1.1.20 creates "internal circuits" primarily consisting of nodes with "useful exit nodes," which allows remote attackers to conduct unspecified statistical attacks...

CVE-2006-3411: Undefined Security Weakness

TLS handshakes in Tor before 0.1.1.20 generate public-private keys based on TLS context rather than the connection, which makes it easier for remote attackers to conduct brute force attacks on the encryption keys...

CVE-2006-3413: Undefined Security Weakness

The privoxy configuration file in Tor before 0.1.1.20, when run on Apple OS X, logs all data via the "logfile", which allows attackers to obtain potentially sensitive information...

CVE-2006-3418: Undefined Security Weakness

Tor before 0.1.1.20 does not validate that a server descriptor's fingerprint line matches its identity key, which allows remote attackers to spoof the fingerprint line, which might be trusted by users or other applications...

CVE-2006-3412: Undefined Security Weakness

Tor before 0.1.1.20 does not sufficiently obey certain firewall options, which allows remote attackers to bypass intended access restrictions for dirservers, direct connections, or proxy servers...

CVE-2006-3415: Undefined Security Weakness

Tor before 0.1.1.20 uses improper logic to validate the "OR" destination, which allows remote attackers to perform a man-in-the-middle MITM attack via unspecified vectors...

CVE-2006-3416: Undefined Security Weakness

Tor before 0.1.1.20 kills the circuit when it receives an unrecognized relay command, which causes network circuits to be disbanded. NOTE: while this item is listed under the "Security fixes" section of the developer changelog, the developer clarified on 20060707 that this is only a self-DoS...