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

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

                      ESB-2009.0536 -- [OpenSolaris]
                         idmap: Denial of service
                               11 June 2009

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

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

Product:              idmap
Publisher:            Sun Microsystems
Operating System:     OpenSolaris
Impact:               Denial of Service
Access:               Existing Account
CVE Names:            CVE-2009-2012

Original Bulletin:    
  http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-66-260508-1

Revision History:     June 11 2009: Document number changed from 
                                    ESB-2009.0692 to ESB-2009.0536
                      June 10 2009: Added CVE Reference
                      June  8 2009: Initial Release

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

Solution Type: Sun Alert
Solution  260508 : A Security Vulnerability in idmap(1M) of OpenSolaris may
                   Allow a Denial of the CIFS (Common Internet File System)
                   Service (DoS)          
Bug ID: 6810842

Product
   OpenSolaris

Date of Resolved Release: 05-Jun-2009

SA Document Body
A security vulnerability in the OpenSolaris idmap(1M) command:

   1. Impact

   A security vulnerability in the OpenSolaris idmap(1M) command may
   allow a local unprivileged user to kill the idpmapd(1M) daemon on a
   CIFS (Common Internet File System/Windows file service) server and
   cause the idmapd(1M) SMF service to transition to the "maintenance"
   state (see smf(5)). This is a type of Denial of Service (DoS).

   2. Contributing Factors

   This issue can occur in the following releases:
   SPARC Platform
     * OpenSolaris based upon builds snv_88 through snv_110

   x86 Platform
     * OpenSolaris based upon builds snv_88 through snv_110

   Note 1: Solaris 8, 9 and 10 are not impacted by this issue as they do
   not support idmap for CIFS.

   Note 2: 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

   Note 3: Only systems that are configured to be a CIFS server are
   impacted by this issue.  To determine if a system is a CIFS server,
   check to see if the SMB server service is online:

     $ svcs svc:/network/smb/server:default
     STATE          STIME    FMRI
     online          9:17:49 svc:/network/smb/server:default

   3. Symptoms

   If the described issue occurs the idmapd(1M) SMF service
   (svc:/system/idmap) will be in the "maintenance" state and one or more
   core files may be generated depending on the configuration of
   coreadm(1M).
   The state of the service can be confirmed by using the following
   command:

     $ svcs svc:/system/idmap

   If a core file is generated, the start of the stack trace (from
   pstack(1) for example) will be similar to the following:

     libc_hwcap2.so.1`strlen+0x30(0, fea4e9bc, a, 5)
     list_mappings_cb+0x71c(fea4ea70, 13, 83b5838, 83b597c)
     sqlite_exec+0xc5(817f818, 821e540, 806410c, fea4ea70, fea4ea6c, 0)
     process_list_svc_sql+0x50(817f818, 80a8514, 821e540, 400, 0, 8)

   4. Workaround

   There is no workaround for this issue.  However, if the described
   issue occurs, the system can be recovered by executing the following
   command as root:

     # svcadm clear svc:/system/idmap:default

   Note: This will only recover from the failure and does not prevent
   further failures.

   5. Resolution

   This issue is addressed in the following releases:
   SPARC Platform
     * OpenSolaris based upon builds snv_111 or later

   x86 Platform
     * OpenSolaris based upon builds snv_111 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

iD8DBQFKMF0cNVH5XJJInbgRAlACAJ4lQyKKeANh9py27C5e3Uo38kCHowCfYGkO
/8PFIrLIOEVWPXs/qFZm4v0=
=QfJi
-----END PGP SIGNATURE-----