blob: bb76d7c59f48a998ac16c32a8420a7898b2ccef4 [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<glsa id="200807-08">
<title>BIND: Cache poisoning</title>
A weakness in the DNS protocol has been reported, which could lead to cache
poisoning on recursive resolvers.
<product type="ebuild">bind</product>
<announced>July 11, 2008</announced>
<revised>July 11, 2008: 01</revised>
<package name="net-dns/bind" auto="yes" arch="*">
<unaffected range="ge">9.4.2_p1</unaffected>
<vulnerable range="lt">9.4.2_p1</vulnerable>
ISC BIND is the Internet Systems Consortium implementation of the
Domain Name System (DNS) protocol.
Dan Kaminsky of IOActive has reported a weakness in the DNS protocol
related to insufficient randomness of DNS transaction IDs and query
source ports.
<impact type="high">
An attacker could exploit this weakness to poison the cache of a
recursive resolver and thus spoof DNS traffic, which could e.g. lead to
the redirection of web or mail traffic to malicious sites.
There is no known workaround at this time.
All BIND users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=net-dns/bind-9.4.2_p1&quot;</code>
Note: In order to utilize the query port randomization to mitigate the
weakness, you need to make sure that your network setup allows the DNS
server to use random source ports for query and that you have not set a
fixed query port via the "query-source port" directive in the BIND
<uri link="">CVE-2008-1447</uri>
<metadata tag="requester" timestamp="Wed, 09 Jul 2008 08:55:27 +0000">
<metadata tag="submitter" timestamp="Wed, 09 Jul 2008 14:42:45 +0000">
<metadata tag="bugReady" timestamp="Fri, 11 Jul 2008 17:35:39 +0000">