-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                               ESB-2009.1569
         Security Vulnerability in BIND DNS Software Shipped With
                   Solaris May Allow DNS Cache Poisoning
                             26 November 2009

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:           BIND
Publisher:         Sun Microsystems
Operating System:  Solaris
                   OpenSolaris
Impact/Access:     Provide Misleading Information -- Remote/Unauthenticated
Resolution:        Mitigation
CVE Names:         CVE-2009-4022  

Reference:         ESB-2009.1561

Original Bulletin: 
   http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-66-273169-1

- --------------------------BEGIN INCLUDED TEXT--------------------

Security Vulnerability in BIND DNS Software Shipped With Solaris May
Allow DNS Cache Poisoning
  _________________________________________________________________

Category : Security
Release Phase : Workaround
Bug Id : 6902912
Product : Solaris 9 Operating System
Solaris 10 Operating System
OpenSolaris
Date of Workaround Release : 24-Nov-2009

A security vulnerability in the BIND DNS software shipped with Solaris:


1. Impact
A security vulnerability in the BIND DNS software shipped with Solaris
may allow a remote user who is able to perform recursive queries to
cause a server that is configured to support DNSSEC validation and
recursive client queries to return incorrect addresses for Internet
hosts, thereby redirecting end users to unintended hosts or services.
This issue is also mentioned in the following document:
  * https://www.isc.org/node/504


2. Contributing Factors
This issue can occur in the following releases:
SPARC Platform
  * Solaris 9
  * Solaris 10
  * OpenSolaris

x86 Platform
  * Solaris 9
  * Solaris 10
  * OpenSolaris

Note 1: BIND shipped with Solaris 8 does not support DNSSEC and is
therefore not impacted by this issue.
Note 2: 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:
$ pgrep in.named && echo "BIND is running"

Note 3: OpenSolaris distributions may include additional bug fixes
above and beyond the build from which it was derived. To determine the
base build of  OpenSolaris, the following command can be used:
 $ uname -v
 snv_86


3. Symptoms
There are no predictable symptoms that would indicate the described
issue has occurred.

4. Workaround
As recursive queries are required to exploit this issue, it is
possible to reduce the likelihood of exploitation by using the
"allow-recursion" option in the "/etc/named.conf" file to restrict the
list of hosts that can perform these queries.
In addition, this issue can be prevented by disabling DNSSEC
functionality. This can be done by setting "dnssec-enable" to "no" in
"/etc/named.conf". Note this may affect the security of DNS
transactions as the facilities provided by DNSSEC will no longer be
available.
For Solaris 10 and OpenSolaris, once the configuration file has been
altered, the DNS service must be restarted by running the svcadm(1)
command as follows:
 # svcadm -v enable svc:/network/dns/server:default
 svc:/network/dns/server:default enabled

followed by:
 # svcadm -v restart svc:/network/dns/server:default
 Action restart set for svc:/network/dns/server:default

In addition, Interim Security Relief (ISR) is available from
http://sunsolve.sun.com/tpatches for the following releases:
SPARC Platform
  * Solaris 9 IDR143418-01
  * Solaris 10 IDR143416-01

x86 Platform
  * Solaris 9 IDR143417-01
  * Solaris 10 IDR143415-01

Note: This document refers to one or more Interim Security Relief
(ISRs) which are designed to address the concerns identified herein.
Sun has limited experience with these (ISRs) due to their interim
nature. As such, you should only install the ISRs on systems meeting
the configurations described above. Sun may release full patches at a
later date, however, Sun is under no obligation whatsoever to create,
release, or distribute any such patch.

5. Resolution
A final resolution is pending completion.
This Sun Alert notification is being provided to you on an "AS IS"
basis. This Sun Alert notification may contain information provided by
third parties. The issues described in this Sun Alert notification may
or may not impact your system(s). Sun makes no representations,
warranties, or guarantees as to the information contained herein. ANY
AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT
YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE
OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN.
This Sun Alert notification contains Sun proprietary and confidential
information. It is being provided to you pursuant to the provisions of
your agreement to purchase services from Sun, or, if you do not have
such an agreement, the Sun.com Terms of Use. This Sun Alert
notification may only be used for the purposes contemplated by these
agreements. 

Copyright 2000-2009 Sun Microsystems, Inc., 4150 Network Circle, Santa
Clara, CA 95054 U.S.A. All rights reserved

- --------------------------END INCLUDED TEXT--------------------

You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.

NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members.  As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.

NOTE: This is only the original release of the security bulletin.  It may
not be updated when updates to the original are made.  If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above.  If you have any questions or need further
information, please contact them directly.

Previous advisories and external security bulletins can be retrieved from:

        http://www.auscert.org.au/render.html?cid=1980

If you believe that your computer system has been compromised or attacked in 
any way, we encourage you to let us know by completing the secure National IT 
Incident Reporting Form at:

        http://www.auscert.org.au/render.html?it=3192

===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072

Internet Email: auscert@auscert.org.au
Facsimile:      (07) 3365 7031
Telephone:      (07) 3365 4417 (International: +61 7 3365 4417)
                AusCERT personnel answer during Queensland business hours
                which are GMT+10:00 (AEST).
                On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967

iD8DBQFLDdibNVH5XJJInbgRAnAzAJ0ewmSchFGIpmT3aYKN0a8vxn19UwCfaTCP
uqWW2nngY7YNzcx1wmw25wc=
=PjSZ
-----END PGP SIGNATURE-----