-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                               ESB-2009.1018
          Ultra-SPARC T2 crypto provider device driver (n2cp(7D))
                                3 July 2009

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:          Ultra-SPARC T2 crypto provider device driver (n2cp(7D))
Publisher:        Sun Microsystems
Operating System: Solaris
                  OpenSolaris
Impact/Access:    Denial of Service -- Remote/Unauthenticated
Resolution:       Patch
CVE Names:        CVE-2009-2137  

- --------------------------BEGIN INCLUDED TEXT--------------------

Solution Type Sun Alert

Solution  258828 :   A Memory Leak in the Solaris Ultra-SPARC T2 crypto 
provider device driver (n2cp(7D)) may Result in Denial of Service (DoS) to 
the System as a Whole  

Bug ID : 6784968

Product

Solaris 10 Operating System
OpenSolaris

Date of Resolved Release : 18-Jun-2009

SA Document Body

A memory leak in the Solaris Ultra-SPARC T2 crypto provider device driver 
(n2cp(7D)) may result in a Denial of Service (DoS) to the system as a 
whole:


1. Impact

A memory leak in the Solaris Ultra-SPARC T2 crypto provider device driver 
(n2cp(7D)) may allow a local or remote unprivileged user to cause Denial of 
Service (DoS) to the system as a whole.

2. Contributing Factors

This issue can occur in the following releases:

SPARC Platform

    * Solaris 10 without patch 140386-03
    * OpenSolaris based upon builds snv_54 through snv_112

Note 1: Solaris 8 and Solaris 9 are not impacted by this issue. Solaris 10 
        and OpenSolaris on the x86 platform is also not impacted.

Note 2: OpenSolaris distributions may include additional bug fixes above and 
        beyond the build from which it was derived. The base build can be 
        derived as follows:

    $ uname -v
    snv_101

This issue only impacts systems with UltraSPARC-T2 CPUs. To determine if a 
system contains this CPU, run the following command:

    $ prtdiag | grep UltraSPARC-T2

If a system is equipped with an UltraSPARC-T2 CPU the output of the above 
command will be similar to the following (output trimmed):

    0      1167 MHz  SUNW,UltraSPARC-T2     on-line  
    1      1167 MHz  SUNW,UltraSPARC-T2     on-line  
    ...
    62     1167 MHz  SUNW,UltraSPARC-T2     on-line  
    63     1167 MHz  SUNW,UltraSPARC-T2     on-line

This issue can be exploited remotely only in cases where there are services 
running on the system that use Solaris Crypto Framework for MAC/HMAC 
processing. To determine if the n2cp driver on the system is used for such 
processing,  run the following command:

    $ kstat -m n2cp | grep mac

If any of  the counters are greater than zero then the driver is used for 
that number of computations.

3. Symptoms

If the described  issue occurs the kernel memory allocations may grow (which 
could be examined using a kernel debugger such as mdb(1)) and messages 
similar to the following may be displayed on the console:

n2cp: [ID 504468 kern.warning] WARNING: 
  alloc_hmac_ctx: keylen(512) > maxlen(32)

The following command can be used to observe the context allocations:

    # echo '::kmastat ! grep n2cp_ctx_cache' | mdb -k

If the value in the 5th column (memory in use) increases over time then the 
issue described in this Sun Alert has occurred.

4. Workaround

To work around the described issue, disable n2cp driver to be used for HMAC 
processing using the following command:

 # /usr/sbin/cryptoadm disable provider=n2cp/0 
 mechanism=CKM_MD5_HMAC,CKM_SHA_1_HMAC,CKM_SHA256_HMAC,CKM_MD5_HMAC_GENERAL,
 CKM_SHA_1_HMAC_GENERAL,CKM_SHA256_HMAC_GENERAL,CKM_SSL3_MD5_MAC,CKM_SSL3_SHA1_MAC

Applying this work around may impact performance of MAC/HMAC processing. For 
example, slowing down SSL connection processing. This impact can be 
noticeable depending on the workload.

5. Resolution

This issue is addressed in the following releases:

SPARC Platform

    * Solaris 10 with patch 140386-03 or later
    * OpenSolaris based upon builds snv_113 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.

- --------------------------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

iD8DBQFKTXLYNVH5XJJInbgRApOjAJwKyKZ7QIRkHpsQ3gwmZynI030XggCfWXlu
B0fAUViVRkp7kEIk1UM7Pfk=
=xOM9
-----END PGP SIGNATURE-----