Note: This is an archival copy of Security Sun Alert 240048 as previously published on http://sunsolve.sun.com.|
Latest version of this security advisory is available from http://support.oracle.com as Sun Alert 1019479.1.
Solaris 8 Operating System
Solaris 9 Operating System
Solaris 10 Operating System
Date of Workaround Release
Date of Resolved Release
DUPLICATE of Sun Alert 239392 - Security Vulnerability in the DNS Protocol may lead to DNS Cache Poisoning
This Sun Alert is a DUPLICATE to Sun Alert 239392, originally issued July 8th, 2008 as an Update.
A security vulnerability in the DNS protocol may allow remote unprivileged users to cause named(1M) to return incorrect addresses for Internet hosts, thereby redirecting end users to unintended hosts or services.
This issue is also referenced in the following documents:
US-CERT Vulnerability Note VU#800113 at http://www.kb.cert.org/vuls/id/800113
CVE-2008-1447 at http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1447
2. Contributing Factors
This issue can occur in the following releases:
OpenSolaris distributions may include additional bug fixes above and beyond the base build from which it was derived. The base build can be derived as follows:
$ uname -a
Only systems with the BIND named(1M) service enabled are impacted by this issue. To verify if BIND is running on a system, the following command can be used:
$ ps -e | grep in.named && echo "BIND is running
There are no predictable symptoms that would indicate the described issue has occurred.
Please refer to section III, "Solution", of CERT VU#800113, in particular the following headings: "Restrict access", "Filter traffic at network perimeters" and Disable recursion:
This issue is addressed in the following releases:
Note 1: The above patches implement mitigation strategies within the implementation of the DNS protocol, specifically source port randomization and query ID randomization making BIND 9 more resilient to an attack. It does not, however, completely remove the possibility of exploitation of this issue.
The full resolution is for DNS Security Extensions (DNSSEC) to be implemented Internet-wide. DNS zone administrators should start signing their zones.
If your site's parent DNS zone is not signed you can register with the ISC's DNSSEC Look-aside Validation (DLV) registry at the following URL:
Further details on configuring your DNA zones for DNSSEC is available from the ISC at the following URL:
Note 2: BIND as provided with Solaris 8 is not DNSSEC capable and thus Sun recommends updating Solaris 8 systems acting as DNS servers to Solaris 10 or later.
Note 3: After installation of the above mentioned patches the named(1M) configuration file, by default /etc/named.conf, MUST not have the "query-source" or "query-source-v6" option configured. These options instruct the name server to use only the port configured for outbound queries which means the source port will not be randomized. When disabling these options note that some firewall configuration may be necessary to allow the name server to work though the firewall.
For more information on Security Sun Alerts, see 1009886.1.
08-Jul-2008: Originally released as Sun Alert 239392
15-Jul-2008: Updated Workaround and Resolution sections
17-Jul-2008: Updated Workaround section
28-Jul-2008: Updated version of 239392 released as Sun Alert 240048
08-Aug-20-08: Updated Contributing Factors and Resolution sections, DUPLICATE of original Sun Alert 239392 for this issue; now Resolved
This solution has no attachment