Microsoft Windows DNS Server Cache Poisoning Vulnerability

Description Microsoft Windows DNS servers are prone to a vulnerability that lets attackers poison DNS caches. This occurs because the software fails to properly handle responses containing data outside of their authority. Successfully exploiting this issue allows remote attackers to poison DNS...

DSA-1605-1 glibc - DNS cache poisoning

Dan Kaminsky discovered that properties inherent to the DNS protocol lead to practical DNS spoofing and cache poisoning attacks. Among other things, successful attacks can lead to misdirected web traffic and email rerouting. At this time, it is not possible to implement the recommended...

DSA-1604-1 bind - DNS cache poisoning

Dan Kaminsky discovered that properties inherent to the DNS protocol lead to practical DNS cache poisoning attacks. Among other things, successful attacks can lead to misdirected web traffic and email rerouting. The BIND 8 legacy code base could not be updated to include the recommended...

FreeBSD -- DNS cache poisoning

Problem Description: The BIND DNS implementation does not randomize the UDP source port when doing remote queries, and the query id alone does not provide adequate randomization. Impact: The lack of source port randomization reduces the amount of data the attacker needs to guess in order to...

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...

Multiple DNS implementations vulnerable to cache poisoning

Overview Deficiencies in the DNS protocol and common DNS implementations facilitate DNS cache poisoning attacks. Description The Domain Name System DNS is responsible for translating host names to IP addresses and vice versa and is critical for the normal operation of internet-connected systems...

DSA-1603-1 bind9 - cache poisoning

Bulletin has no description...

tomcat multiple content-length header poisioning

Jakarta Tomcat 5.0.19 Coyote/1.1 and Tomcat 4.1.24 Coyote/1.0 allows remote attackers to poison the web cache, bypass web application firewall protection, and conduct XSS attacks via an HTTP request with both a "Transfer-Encoding: chunked" header and a Content-Length header, which causes Tomcat t...

Multiple Cybozu products vulnerable to HTTP header injection

Overview Multiple Cybozu products are vulnerable to HTTP header injection. Multiple Cybozu products are vulnerable to HTTP header injection because they do not properly process HTTP headers. Impact A remote attacker can conduct cache poisoning, send an arbitrary cookie, or execute an arbitrary...

tomcat multiple content-length header poisioning

Jakarta Tomcat 5.0.19 Coyote/1.1 and Tomcat 4.1.24 Coyote/1.0 allows remote attackers to poison the web cache, bypass web application firewall protection, and conduct XSS attacks via an HTTP request with both a "Transfer-Encoding: chunked" header and a Content-Length header, which causes Tomcat t...

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...

Debian Security Advisory DSA 1544-1 (pdns-recursor)

The remote host is missing an update to pdns-recursor announced via advisory DSA 1544-1. This VT has been deprecated and merged into the VT SPDX-FileCopyrightText: 2008 E-Soft Inc. Some text descriptions might be excerpted from a referenced sources, and are Copyright C by the respective right...

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...

Debian DSA-1544-2 : pdns-recursor - design flaw

Amit Klein discovered that pdns-recursor, a caching DNS resolver, uses a weak random number generator to create DNS transaction IDs and UDP source port numbers. As a result, cache poisoning attacks were simplified. CVE-2008-1637 and CVE-2008-3217 %NASLMINLEVEL 70300 C Tenable Network Security, In...

FreeBSD : powerdns-recursor -- DNS cache poisoning (b21790a5-02fb-11dd-bd06-0017319806e7)

If the system random number generator can be predicted by its past output, then an attacker may spoof Recursor to accept mallicious data. This leads to DNS cache poisoning and client redirection. %NASLMINLEVEL 70300 C Tenable Network Security, Inc. The descriptive text and package checks in this...

[SECURITY] [DSA 1544-1] New pdns-recursor packages fix cache poisoning vulnerability

---------------------------------------------------------------------- Debian Security Advisory DSA-1544-1 [email protected] http://www.debian.org/security/ Florian Weimer April 09, 2008 http://www.debian.org/security/faq - ----------------------------------------------------------------------...

DSA-1544-1 pdns-recursor - cache poisoning vulnerability

Bulletin has no description...

Microsoft Windows DNS Stub Resolver Cache Poisoning (MS08-020)

Hello BugTraq, The Microsoft Windows DNS stub resolver the component in Windows that queries the upstream DNS server for address resolutions on behalf of most Windows programs, e.g. browsers sends predictable DNS queries with respect to DNS transaction ID and source UDP port. This allows some...

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...

DEBIAN-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...