Dnsmasq DNS cache poisoning
| dnsmasq-dns-cache-poisoning (19826) |  Medium Risk |
Description:
Dnsmasq could allow a remote attacker to perform DNS cache poisoning. Once a DNS reply is received, only the 16-bit ID is checked against the current query. If a remote attacker sends a flood of DNS (Domain Name Server) replies to Dnsmasq and guesses a valid ID, the attacker could perform DNS cache poisoning on the system.
Platforms Affected:
- Simon Kelley, Dnsmasq prior to 2.21
Remedy:
Upgrade to the latest version of Dnsmasq (2.21 or later), available from the Dnsmasq Index Web page. See References.
Consequences:
Bypass Security
References:
- Dnsmasq Index Web page, Index of /dnsmasq at http://www.thekelleys.org.uk/dnsmasq/.
- Dnsmasq Web page, Dnsmasq at http://www.thekelleys.org.uk/dnsmasq/doc.html.
- BID-12897: Dnsmasq Multiple Remote Vulnerabilities
- CVE-2005-0877: Dnsmasq before 2.21 allows remote attackers to poison the DNS cache via answers to queries that were not made by Dnsmasq.
- GLSA-200504-03: Dnsmasq: Poisoning and Denial of Service vulnerabilities
- SA14691: Dnsmasq DHCP Lease File Denial of Service and DNS Cache Poisoning
- SUSE-SR:2005:011: SUSE Security Summary Report
Reported:
Mar 25, 2005
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net