Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =========================================================================== AUSCERT External Security Bulletin Redistribution ESB-2009.0243 -- [Solaris] Security Vulnerability in the Solaris keysock 16 March 2009 =========================================================================== AusCERT Security Bulletin Summary --------------------------------- Product: Solaris 10 OpenSolaris Publisher: Sun Microsystems Operating System: Solaris Impact: Denial of Service Access: Existing Account Original Bulletin: http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-66-253568-1 - --------------------------BEGIN INCLUDED TEXT-------------------- Solution Type: Sun Alert Solution 253568 : Security Vulnerability in the Solaris keysock Kernel Module may Lead to a System Panic Bug ID: 6797746 Product Solaris 10 Operating System OpenSolaris Date of Resolved Release: 13-Mar-2009 SA Document Body Security vulnerability in the Solaris keysock kernel module may lead to a system panic 1. Impact A security vulnerability in the Solaris 10 keysock kernel module may allow local users with sufficient privileges to create PF_KEY (see pf_key(7P)) sockets to be able to cause a system panic thereby resulting in a 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 141008-01 * OpenSolaris based upon builds snv_01 through snv_108 x86 Platform * Solaris 10 without patch 141009-01 * OpenSolaris based upon builds snv_01 through snv_108 Note: 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 3. Symptoms If the described issue occurs, the system may panic with a stack trace similar to the following: vpanic() mutex_vector_enter() keysock_opt_set() svr4_optcom_req() keysock_wput_other() putnext() strput() kstrputmsg() sotpi_setsockopt() setsockopt() syscall_trap32() 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 141008-01 or later * OpenSolaris based upon builds snv_109 or later x86 Platform * Solaris 10 with patch 141009-01 or later * OpenSolaris based upon builds snv_109 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 iD8DBQFJvc41NVH5XJJInbgRAnnVAJwN8i9+hZYlN5aMohIEXfLGSQWp1gCfQESq qBJ9WTIy46qYX20z2Pdwoxw= =Ul4X -----END PGP SIGNATURE-----