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

---

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 without patch 141930-01
  
• OpenSolaris based upon builds snv_01 through snv_117

x86 Platform

• Solaris 10 without patch 141931-01
  
• OpenSolaris based upon builds snv_01 through snv_117

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

There is no workaround for this issue.  Please see the Resolution section below.

5. Resolution

This issue is addressed in the following releases:

SPARC Platform

• Solaris 10 with patch 141930-01 or later
• OpenSolaris based upon builds snv_118 or later

x86 Platform

• Solaris 10 with patch 141931-01 or later
  
• OpenSolaris based upon builds snv_118 or later

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.


Modification History

20-Jul-2009: Updated Contributing Factors and Resolution sections.
28-Jul-2009: Updated Contributing Factors and Resolution sections. Resolved.

Attachments

This solution has no attachment