summaryrefslogtreecommitdiff
blob: 2ac89d018fbdf7fc26d75537cd53a9df7f9d3b6b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200609-11">
  <title>BIND: Denial of Service</title>
  <synopsis>
    ISC BIND contains two vulnerabilities allowing a Denial of Service under
    certain conditions.
  </synopsis>
  <product type="ebuild">bind</product>
  <announced>2006-09-15</announced>
  <revised count="01">2006-09-15</revised>
  <bug>146486</bug>
  <access>remote</access>
  <affected>
    <package name="net-dns/bind" auto="yes" arch="*">
      <unaffected range="ge">9.3.2-r4</unaffected>
      <unaffected range="rge">9.2.6-r4</unaffected>
      <vulnerable range="lt">9.3.2-r4</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    ISC BIND is the Internet Systems Consortium implementation of the
    Domain Name System (DNS) protocol.
    </p>
  </background>
  <description>
    <p>
    Queries for SIG records will cause an assertion error if more than one
    SIG RRset is returned. Additionally, an INSIST failure can be triggered
    by sending multiple recursive queries if the response to the query
    arrives after all the clients looking for the response have left the
    recursion queue.
    </p>
  </description>
  <impact type="normal">
    <p>
    An attacker having access to a recursive server can crash the server by
    querying the SIG records where there are multiple SIG RRsets, or by
    sending many recursive queries in a short time. The exposure can be
    lowered by restricting the clients that can ask for recursion. An
    attacker can also crash an authoritative server serving a DNSSEC zone
    in which there are multiple SIG RRsets.
    </p>
  </impact>
  <workaround>
    <p>
    There are no known workarounds at this time.
    </p>
  </workaround>
  <resolution>
    <p>
    All BIND 9.3 users should update to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=net-dns/bind-9.3.2-r4"</code>
    <p>
    All BIND 9.2 users should update to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=net-dns/bind-9.2.6-r4"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4095">CVE-2006-4095</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-4096">CVE-2006-4096</uri>
  </references>
  <metadata tag="requester" timestamp="2006-09-06T10:13:53Z">
    falco
  </metadata>
  <metadata tag="submitter" timestamp="2006-09-07T11:28:27Z">
    falco
  </metadata>
  <metadata tag="bugReady" timestamp="2006-09-14T22:49:56Z">
    jaervosz
  </metadata>
</glsa>