glsa-201206-01.xml


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

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201206-01">
  <title>BIND: Multiple vulnerabilities</title>
  <synopsis>Multiple vulnerabilities have been found in BIND, the worst of
    which allowing to cause remote Denial of Service.
  </synopsis>
  <product type="ebuild">bind</product>
  <announced>2012-06-02</announced>
  <revised>2012-06-02: 1</revised>
  <bug>347621</bug>
  <bug>356223</bug>
  <bug>368863</bug>
  <bug>374201</bug>
  <bug>374623</bug>
  <bug>390753</bug>
  <access>remote</access>
  <affected>
    <package name="net-dns/bind" auto="yes" arch="*">
      <unaffected range="ge">9.7.4_p1</unaffected>
      <vulnerable range="lt">9.7.4_p1</vulnerable>
    </package>
  </affected>
  <background>
    <p>BIND is the Berkeley Internet Name Domain Server.</p>
  </background>
  <description>
    <p>Multiple vulnerabilities have been discovered in BIND. Please review the
      CVE identifiers referenced below for details.
    </p>
  </description>
  <impact type="normal">
    <p>The vulnerabilities allow remote attackers to cause a Denial of Service
      (daemon crash) via a DNS query, to bypass intended access restrictions,
      to incorrectly cache a ncache entry and a rrsig for the same type and to
      incorrectly mark zone data as insecure.
    </p>
  </impact>
  <workaround>
    <p>There is no known workaround at this time.</p>
  </workaround>
  <resolution>
    <p>All bind users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=net-dns/bind-9.7.4_p1"
    </code>
    
    <p>NOTE: This is a legacy GLSA. Updates for all affected architectures are
      available since December 22, 2011. It is likely that your system is
      already
      no longer affected by this issue. 
    </p>
  </resolution>
  <references>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3613">CVE-2010-3613</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3614">CVE-2010-3614</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3615">CVE-2010-3615</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-3762">CVE-2010-3762</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-0414">CVE-2011-0414</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-1910">CVE-2011-1910</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-2464">CVE-2011-2464</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-2465">CVE-2011-2465</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-4313">CVE-2011-4313</uri>
  </references>
  <metadata timestamp="2011-10-07T23:37:02Z" tag="requester">craig</metadata>
  <metadata timestamp="2012-06-02T13:53:49Z" tag="submitter">craig</metadata>
</glsa>