summaryrefslogtreecommitdiff
path: root/metadata/glsa/glsa-200812-19.xml
blob: 6b0d02eb4dae05e0d65c51511b3428fa34e0aee7 (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
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200812-19">
  <title>PowerDNS: Multiple vulnerabilities</title>
  <synopsis>
    Two vulnerabilities have been discovered in PowerDNS, possibly leading to a
    Denial of Service and easing cache poisoning attacks.
  </synopsis>
  <product type="ebuild">pdns</product>
  <announced>2008-12-19</announced>
  <revised count="01">2008-12-19</revised>
  <bug>234032</bug>
  <bug>247079</bug>
  <access>remote</access>
  <affected>
    <package name="net-dns/pdns" auto="yes" arch="*">
      <unaffected range="ge">2.9.21.2</unaffected>
      <vulnerable range="lt">2.9.21.2</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    The PowerDNS Nameserver is an authoritative-only nameserver which uses
    a flexible backend architecture.
    </p>
  </background>
  <description>
    <p>
    Daniel Drown reported an error when receiving a HINFO CH query
    (CVE-2008-5277). Brian J. Dowling of Simplicity Communications
    discovered a previously unknown security implication of the PowerDNS
    behavior to not respond to certain queries it considers malformed
    (CVE-2008-3337).
    </p>
  </description>
  <impact type="normal">
    <p>
    A remote attacker could send specially crafted queries to cause a
    Denial of Service. The second vulnerability in itself does not pose a
    security risk to PowerDNS Nameserver. However, not answering a query
    for an invalid DNS record within a valid domain allows for a larger
    spoofing window on third-party nameservers for domains being hosted by
    PowerDNS Nameserver itself.
    </p>
  </impact>
  <workaround>
    <p>
    There is no known workaround at this time.
    </p>
  </workaround>
  <resolution>
    <p>
    All PowerDNS users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=net-dns/pdns-2.9.21.2"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-3337">CVE-2008-3337</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5277">CVE-2008-5277</uri>
  </references>
  <metadata tag="requester" timestamp="2008-09-06T21:05:59Z">
    p-y
  </metadata>
  <metadata tag="bugReady" timestamp="2008-09-06T21:06:12Z">
    p-y
  </metadata>
  <metadata tag="submitter" timestamp="2008-09-10T17:38:51Z">
    jaervosz
  </metadata>
</glsa>