Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2009.0474 -- [Solaris][OpenSolaris]
Solaris SASL: Denial of Service
18 May 2009
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: Solaris SASL
Publisher: Sun Microsystems
Operating System: Solaris 10
OpenSolaris
Impact: Denial of Service
Access: Remote/Unauthenticated
CVE Names: CVE-2009-0688
Ref: AL-2009.0040
Original Bulletin:
http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-66-259148-1
- --------------------------BEGIN INCLUDED TEXT--------------------
Solution Type: Sun Alert
Solution 259148 : Security Vulnerability in the Solaris Simple
Authentication and Security Layer (SASL) Library (see libsasl(3LIB))
Routine sasl_encode64(3SASL) may Allow Unprivileged Users to Crash
Applications Using this Function
Bug ID: 6836899
Product
Solaris 10 Operating System
OpenSolaris
Date of Workaround Release: 14-May-2009
SA Document Body
Security vulnerability in the Solaris Simple Authentication and Security Layer
(SASL) Library (see libsasl(3LIB)) routine sasl_encode64(3SASL):
1. Impact
A buffer overflow security vulnerability in the Solaris Simple
Authentication and Security Layer (SASL) library (see libsasl(3LIB))
routine sasl_encode64(3SASL) may allow local or remote unprivileged
users to crash applications which use this function.
Solaris LDAP client (ldap(1)), sendmail(1M) and Solaris iSCSI
implementation are examples of applications which use the vulnerable
library.
This vulnerability is also described in the following documents:
CERT Vulnerability Note VU#238019 at:
* http://www.kb.cert.org/vuls/id/238019
CVE CVE-2009-0688 at:
* http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0688
2. Contributing Factors
This issue can occur in the following releases:
SPARC Platform
* Solaris 10
* OpenSolaris based upon builds snv_01 through snv_114
x86 Platform
* Solaris 10
* OpenSolaris based upon builds snv_01 through snv_114
Note 1: Solaris libsasl(3LIB) is based on the the Cyrus SASL code
base.
Note 2: Solaris 8 and Solaris 9 are not impacted by this issue.
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
To determine if an application has a dynamic dependency on the
libsasl(3LIB) library, the ldd(1) utility can be used:
$ ldd /usr/lib/sendmail |grep libsasl
libsasl.so.1 => /usr/lib/libsasl.so.1
Note: Some applications may use libsasl(3LIB) but not report
libsasl(3LIB) as a dynamic dependency with ldd(1) if the library is
loaded by dlopen(3C). Therefore, to display all shared objects used
by an application, pldd(1) should be used against the running process:
# pldd <pid of application> | grep libsasl
/usr/lib/libsasl.so.1
3. Symptoms
If the described issue occurs, the application which links to the
libsasl(3LIB) library will crash, potentially leaving a core file
depending on the system configuration.
4. Workaround
Interim Security Relief (ISR) is available from
http://sunsolve.sun.com/tpatches for the following releases:
SPARC Platform
* Solaris 10 IDR141683-01
x86 Platform
* Solaris 10 IDR141684-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.
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
iD8DBQFKEPYhNVH5XJJInbgRAhjpAJ9Wn1E9uehLqHSIrxAbckNX9e3dIwCePe8m
+RabYFm/yx7Qb5ZC+v+h5Qk=
=NOdN
-----END PGP SIGNATURE-----