Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2009.0098 -- [Solaris]
Security Vulnerability in Solaris BIND named(1M) due to
Incorrect DNSSEC Signature Verification
16 February 2009
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: Solaris 9 Operating System
Solaris 10 Operating System
OpenSolaris
Publisher: Sun Microsystems
Operating System: Solaris
OpenSolaris
Impact: Provide Misleading Information
Access: Remote/Unauthenticated
CVE Names: CVE-2009-0025
Ref: ESB-2009.0017
Original Bulletin:
http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-66-250846-1
Revision History: February 16 2009: Solaris 10 Patches Released
January 29 2009: Initial Release
- --------------------------BEGIN INCLUDED TEXT--------------------
Solution Type: Sun Alert
Solution 250846 : Security Vulnerability in Solaris BIND named(1M)
due to Incorrect DNSSEC Signature Verification
Bug ID: 6791029
Product
Solaris 9 Operating System
Solaris 10 Operating System
OpenSolaris
Date of Workaround Release: 27-Jan-2009
SA Document Body
Security vulnerability in Solaris BIND named(1M) due to incorrect DNSSEC
signature verification:
1. Impact
An insufficient validation vulnerability in named(1m) due to
incorrectly processing the return value of OpenSSL library functions
"EVP_VerifyFinal()" and "DSA_do_verify()" may allow a remote
unprivileged user to trick named(1m) into believing DNSSEC signatures
that should not have passed validation, and subsequently forge DNS
responses and redirect Internet services.
Sun acknowledges with thanks, Google Security Team (for the original
OpenSSL issue), Florian Weimer for spotting that BIND was vulnerable
and the ISC for for bringing this issue to our attention.
This issue is also referenced in the following documents:
* CVE-2009-0025 at:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0025
* https://www.isc.org/node/389
2. Contributing Factors
This issue can occur in the following releases:
SPARC Platform
* Solaris 9 with patch 112837-15
* Solaris 10 without patch 119783-09
* OpenSolaris based upon builds snv_01 through snv_106
x86 Platform
* Solaris 9 with patch 114265-14
* Solaris 10 without patch 119784-09
* OpenSolaris based upon builds snv_01 through snv_106
Note 1: Solaris 8 is not impacted by this issue as it does not support
DNSSEC.
Note 2: This issue only occurs on systems that are running BIND 9
where the named(1M) version is less than and not equal to 9.3.6-P1,
and the service is running and accepting DNSSEC responses using the
DNSKEY algorithms DSA(3).
To determine if a system meets the above criteria, execute the
following commands:
1. Determine if Sun's BIND server is installed and if the version is
affected:
Solaris 9 Systems:
# pkginfo SUNWinamd || echo "BIND server not installed"
# /usr/lib/dns/named -v
Solaris 10 Systems and OpenSolaris:
# pkginfo SUNWbind || echo "BIND server not installed"
# /usr/sbin/named -v
2. Determine if BIND is configured and enabled by checking for the
following process:
# ps -e | grep named && echo "BIND is running"
3. Determine if BIND is configured to use DNSSEC:
# grep -i "dnssec-enable.*yes" /etc/named.conf
4. Determine that BIND is accepting DSA-only signed responses:
# grep -i "disable-algorithms.*dsa" /etc/named.conf
Note: Points 3 and 4 above should be confirmed by carefully checking
the configuration file as it is possible that the lines are actually
commented out.
3. Symptoms
There are no predictable symptoms that would indicate the described
issue has occurred.
4. Workaround
To workaround the described issue, disable the compromised algorithm
in named.conf by adding the following line:
disable-algorithms . { DSA; };
This will cause answers from zones signed only with DSA (3) to be
treated as insecure.
5. Resolution
This issue is addressed in the following releases:
SPARC Platform
* Solaris 10 with patch 119783-09 or later
* OpenSolaris based upon builds snv_107 or later
x86 Platform
* Solaris 10 with patch 119784-09 or later
* OpenSolaris based upon builds snv_107 or later
A final resolution is pending completion for Solaris 9.
For more information on Security Sun Alerts, see Technical
Instruction ID 213557.
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
iD8DBQFJmPt9NVH5XJJInbgRAst0AJ9MDGwEXqzcjApF5Jt0TG45W/8SmACfdd1a
x2H0ywyeSDoTWPiCTD6raf4=
=Tk4H
-----END PGP SIGNATURE-----