231 matches found
CVE-2008-1447
The DNS protocol, as implemented in 1 BIND 8 and 9 before 9.5.0-P1, 9.4.2-P1, and 9.3.5-P1; 2 Microsoft DNS in Windows 2000 SP4, XP SP2 and SP3, and Server 2003 SP1 and SP2; and other implementations allow remote attackers to spoof DNS traffic via a birthday attack that uses in-bailiwick referral...
CVE-2008-1447
The DNS protocol, as implemented in 1 BIND 8 and 9 before 9.5.0-P1, 9.4.2-P1, and 9.3.5-P1; 2 Microsoft DNS in Windows 2000 SP4, XP SP2 and SP3, and Server 2003 SP1 and SP2; and other implementations allow remote attackers to spoof DNS traffic via a birthday attack that uses in-bailiwick referral...
GLSA-200804-22 : PowerDNS Recursor: DNS Cache Poisoning
The remote host is affected by the vulnerability described in GLSA-200804-22 PowerDNS Recursor: DNS Cache Poisoning Amit Klein of Trusteer reported that insufficient randomness is used to calculate the TRXID values and the UDP source port numbers CVE-2008-1637. Thomas Biege of SUSE pointed out th...
PowerDNS Recursor: DNS Cache Poisoning
Background The PowerDNS Recursor is an advanced recursing nameserver. Description Amit Klein of Trusteer reported that insufficient randomness is used to calculate the TRXID values and the UDP source port numbers CVE-2008-1637. Thomas Biege of SUSE pointed out that a prior fix to resolve this iss...
CVE-2008-1637
PowerDNS Recursor before 3.1.5 uses insufficient randomness to calculate 1 TRXID values and 2 UDP source port numbers, which makes it easier for remote attackers to poison a DNS cache, related to a algorithmic deficiencies in rand and random functions in external libraries, b use of a 32-bit seed...
CVE-2001-0950
CVE-2001-0950 concerns the ValiCert Enterprise Validation Authority (EVA) Administration Server, version 3.3–4.2.1. The root cause is the use of insufficiently random data: session tokens for HSMs are generated with the C rand() function, and certificate/key generation may rely on /dev/urandom in...
CVE-2001-0950
ValiCert Enterprise Validation Authority EVA Administration Server 3.3 through 4.2.1 uses insufficiently random data to 1 generate session tokens for HSMs using the C rand function, or 2 generate certificates or keys using /dev/urandom instead of another source which blocks when the entropy pool ...
Keys generated with PGP5i batch mode do not contain sufficient randomness on systems that use /dev/random
Overview Under certain circumstances, PGP v5.0 generates keys that are not sufficiently random, which may allow an attacker to predict keys and, hence, recover information encrypted with that key. Description Generating Randomness in PGP Keys In order to generate cryptographically secure keys, PG...
CVE-2000-0445
The pgpk command in PGP 5.x on Unix systems uses an insufficiently random data source for non-interactive key pair generation, which may produce predictable keys...
CVE-2000-0445
The CVE-2000-0445 issue affects PGP 5.x on Unix-like systems where non-interactive (batch) key generation via pgpk can use insufficient randomness collected from /dev/random. The root cause is how PGP v5.0 processes entropy when generating keys in unattended mode, potentially producing weak, pred...