Note: This is an archival copy of Security Sun Alert 267031 as previously published on http://sunsolve.sun.com.|
Latest version of this security advisory is available from http://support.oracle.com as Sun Alert 1020905.1.
Solaris 9 Operating System
Solaris 10 Operating System
Sun Java Enterprise System 5
Sun Java Enterprise System 2005
Date of Resolved Release
A heap overflow vulnerability in Network Security Services (NSS):
A heap overflow vulnerability in Network Security Services (NSS) may allow a remote SSL server to cause a Denial of Service (DoS) to SSL client applications or to possibly execute arbitrary code with the privileges of the SSL client application, via a long domain name in the subject's Common Name (CN) field of an X.509 certificate, related to the "cert_TestHostName" function.
Firefox, Thunderbird, Pidgin and Evolution are examples of vulnerable SSL client applications.
This issue is also described in the following document:
CVE-2009-2404 at: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2404
2. Contributing Factors
This issue can occur in the following releases:
Note 2: To determine if a package or a patch is installed on a system, follow these instructions:
To determine if the package SUNWtls is installed, the following command may be used:
$ /usr/bin/pkginfo -l SUNWtlsLinux Platform
To determine if the package "sun-nss" is installed and the version of the installed package, the following command may be used:
$ /bin/rpm -q sun-nssNote: Linux "sun-nss" packages 3.12.2 and earlier are vulnerable to this issue.
To determine if the package "sun-nss" is installed, the following command may be used:
$ /usr/sbin/swlist sun-nssTo determine which patch level for "sun-nss" is installed, the following command may be used:
$ /usr/sbin/swlist 124379\*Windows Platform
To determine if "Sun Java Enterprise System" is installed, look into "Add or Remove Programs" from the "Control Panel" and check if "Sun Java(TM) Enterprise System 2005Q4" or"Sun Java(TM) Enterprise System 5" is listed as being currently installed.
To determine the list of JES patches installed on the system, the following command may be used:
<JES installation directory>\utils\patch\ListJavaESPatches.exeNote 3: All systems with NSS versions prior to NSS 3.12.3 are potentially vulnerable to this issue.
Systems with NSS 3.12.3 using the environment variable named "NSS_USE_SHEXP_IN_CERT_NAME" are also potentially vulnerable.
Systems with NSS 3.12.3 NOT using the environment variable named "NSS_USE_SHEXP_IN_CERT_NAME" are NOT vulnerable.
Systems with NSS 3.12.4 (and later versions), wether or not using the environment variable named "NSS_USE_SHEXP_IN_CERT_NAME", are NOT vulnerable.
There are no symptoms that would indicate the described issue has been exploited to execute abitrary code. A crafted X.509 certificate which may trigger the vulnerability would contain an unusually long domain name in the Common Name (CN) field.
To work around the described issue on systems with NSS 3.12.3 only, do not set the "NSS_USE_SHEXP_IN_CERT_NAME" environment variable.
This issue is addressed in the following releases WITHOUT the environment variable NSS_USE_SHEXP_IN_CERT_NAME set:
For more information on Security Sun Alerts, see 1009886.1.
Copyright 2000-2009 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.
This solution has no attachment