summaryrefslogtreecommitdiff
blob: bf8f1bd6415f6433fa7299b3f66eb3b1e03d0a24 (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
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201701-26">
  <title>BIND: Denial of Service</title>
  <synopsis>A vulnerability in BIND might allow remote attackers to cause a
    Denial of Service condition.
  </synopsis>
  <product type="ebuild">bind</product>
  <announced>January 11, 2017</announced>
  <revised>January 11, 2017: 1</revised>
  <bug>598750</bug>
  <access>remote</access>
  <affected>
    <package name="net-dns/bind" auto="yes" arch="*">
      <unaffected range="ge">9.10.4_p4</unaffected>
      <vulnerable range="lt">9.10.4_p4</vulnerable>
    </package>
  </affected>
  <background>
    <p>BIND (Berkeley Internet Name Domain) is a Name Server.</p>
  </background>
  <description>
    <p>A defect in BIND’s handling of responses containing a DNAME answer can
      cause a resolver to exit after encountering an assertion failure in db.c
      or resolver.c.
    </p>
  </description>
  <impact type="normal">
    <p>A remote attacker could send a specially crafted DNS request to the BIND
      resolver possibly resulting in a Denial of Service condition.
    </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.10.4_p4"
    </code>
  </resolution>
  <references>
    <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-8864">CVE-2016-8864</uri>
  </references>
  <metadata tag="requester" timestamp="Wed, 04 Jan 2017 02:59:06 +0000">b-man</metadata>
  <metadata tag="submitter" timestamp="Wed, 11 Jan 2017 12:27:02 +0000">whissi</metadata>
</glsa>