Some vulnerabilities have been reported in dnsmasq, which can be exploited by malicious people to cause a DoS (Denial of Service) and poison the DNS cache.

1) A vulnerability is caused due to dnsmasq not sufficiently randomising the DNS transaction ID and the source port number, which can be exploited to poison the DNS cache.

2) An error when an unknown client tries to renew a DHCP lease can be exploited to crash the service.

Note: Additionally, an error within the netlink code and a potential crash when a host without a lease performs a DHCPINFORM have been reported in version 2.43.

Vulnerability #1 is reported in versions prior to 2.43, vulnerability #2 is reported in version 2.43.

Solution
Update to version 2.45.

Provided and/or discovered by
1) Dan Kaminsky, IOActive
2) The vendor thanks Carlos Carvalho

Changelog
Further details available in Customer Area

Original Advisory
dnsmasq release announcements:
http://article.gmane.org/gmane.network.dns.dnsmasq.general/2156
http://article.gmane.org/gmane.network.dns.dnsmasq.general/2189
http://article.gmane.org/gmane.network.dns.dnsmasq.general/2199

Vendor statement regarding DNS cache poisoning:
http://article.gmane.org/gmane.network.dns.dnsmasq.general/2176

Deep Links
Links available in Customer Area