glsa-200901-03.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
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="200901-03">
  <title>pdnsd: Denial of Service and cache poisoning</title>
  <synopsis>
    Two errors in pdnsd allow for Denial of Service and cache poisoning.
  </synopsis>
  <product type="ebuild">pdnsd</product>
  <announced>2009-01-11</announced>
  <revised count="01">2009-01-11</revised>
  <bug>231285</bug>
  <access>remote</access>
  <affected>
    <package name="net-dns/pdnsd" auto="yes" arch="*">
      <unaffected range="ge">1.2.7</unaffected>
      <vulnerable range="lt">1.2.7</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    pdnsd is a proxy DNS server with permanent caching that is designed to
    cope with unreachable DNS servers.
    </p>
  </background>
  <description>
    <p>
    Two issues have been reported in pdnsd:
    </p>
    <ul>
    <li>
    The p_exec_query() function in src/dns_query.c does not properly handle
    many entries in the answer section of a DNS reply, related to a
    "dangling pointer bug" (CVE-2008-4194).
    </li>
    <li>
    The default value for query_port_start was set to 0, disabling UDP
    source port randomization for outgoing queries (CVE-2008-1447).
    </li>
    </ul>
  </description>
  <impact type="normal">
    <p>
    An attacker could exploit the second weakness to poison the cache of
    pdnsd and thus spoof DNS traffic, which could e.g. lead to the
    redirection of web or mail traffic to malicious sites. The first issue
    can be exploited by enticing pdnsd to send a query to a malicious DNS
    server, or using the port randomization weakness, and might lead to a
    Denial of Service.
    </p>
  </impact>
  <workaround>
    <p>
    Port randomization can be enabled by setting the "query_port_start"
    option to 1024 which would resolve the CVE-2008-1447 issue.
    </p>
  </workaround>
  <resolution>
    <p>
    All pdnsd users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=net-dns/pdnsd-1.2.7"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1447">CVE-2008-1447</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-4194">CVE-2008-4194</uri>
  </references>
  <metadata tag="requester" timestamp="2008-11-26T18:15:10Z">
    rbu
  </metadata>
  <metadata tag="submitter" timestamp="2008-11-26T23:10:06Z">
    rbu
  </metadata>
  <metadata tag="bugReady" timestamp="2008-11-26T23:10:19Z">
    rbu
  </metadata>
</glsa>