Note: This is an archival copy of Security Sun Alert 259148 as previously published on http://sunsolve.sun.com.|
Latest version of this security advisory is available from http://support.oracle.com as Sun Alert 1020474.1.
Solaris 10 Operating System
Date of Workaround Release
Date of Resolved Release
Security vulnerability in the Solaris Simple Authentication and Security Layer (SASL) Library (see libsasl(3LIB)) routine sasl_encode64(3SASL):
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:
This issue can occur in the following releases:
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 -vTo 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 libsaslNote: 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
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.
There is no workaround for this issue. Please see the Resolution section below.
This issue is addressed in the following releases:
Copyright 2000-2009 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.
20-Jul-2009: Updated Contributing Factors and Resolution sections.
28-Jul-2009: Updated Contributing Factors and Resolution sections. Resolved.
This solution has no attachment