Two errors in pdnsd allow for Denial of Service and cache poisoning.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| net-dns/pdnsd | * | < 1.2.7 | >= 1.2.7 |
pdnsd is a proxy DNS server with permanent caching that is designed to cope with unreachable DNS servers.
Two issues have been reported in pdnsd:
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.
Port randomization can be enabled by setting the "query_port_start" option to 1024 which would resolve the CVE-2008-1447 issue.
All pdnsd users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=net-dns/pdnsd-1.2.7"
pdnsd is vulnerable to a buffer overflow that may result in arbitrary code execution.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| net-dns/pdnsd | * | < 1.2.4 | >= 1.2.4 |
pdnsd is a proxy DNS server with permanent caching that is designed to cope with unreachable DNS servers.
The pdnsd team has discovered an unspecified buffer overflow vulnerability. The PROTOS DNS Test Suite, by the Oulu University Secure Programming Group (OUSPG), has also revealed a memory leak error within the handling of the QTYPE and QCLASS DNS queries, leading to consumption of large amounts of memory.
An attacker can craft malicious DNS queries leading to a Denial of Service, and potentially the execution of arbitrary code.
There is no known workaround at this time.
All pdnsd users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=net-dns/pdnsd-1.2.4-r1"