Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =========================================================================== AUSCERT External Security Bulletin Redistribution ESB-2007.1033 -- [Solaris] Solaris 9 sshd(1M) Patches May Cause Incorrect Audit Data to be Logged 20 December 2007 =========================================================================== AusCERT Security Bulletin Summary --------------------------------- Product: Solaris Auditing Publisher: Sun Microsystems Operating System: Solaris 9 Impact: Provide Misleading Information Access: Existing Account Original Bulletin: http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-26-103172-1 - --------------------------BEGIN INCLUDED TEXT-------------------- Sun(sm) Alert Notification * Sun Alert ID: 103172 * Synopsis: Solaris 9 sshd(1M) Patches May Cause Incorrect Audit Data to be Logged * Category: Security, Availability * Product: Solaris 9 Operating System * BugIDs: 6612944 * Avoidance: Patch * State: Resolved * Date Released: 18-Dec-2007 * Date Closed: 18-Dec-2007 * Date Modified: 1. Impact Solaris 9 systems with Solaris Auditing (see bsmconv(1M)) enabled and with the sshd(1M) patches installed as listed in section 2 below will contain audit records with an incorrect audit-ID. In addition, incomplete audit classes may be selected for users logging in via ssh(1). 2. Contributing Factors This issue can occur in the following releases: SPARC Platform * Solaris 9 with patches 113273-11 through 113273-16 and without patch 122300-17 x86 Platform * Solaris 9 with patches 114858-09 through 114858-13 and without patch 122301-17 Notes: 1. This issue does not affect Solaris 10. 2. Solaris 8 does not ship with SSH and thus is not impacted by this issue. 3. This issue only affects systems which have Solaris Auditing enabled (see bsmconv(1M)). To determine if Solaris Auditing is enabled on a system, a command such as the following can be used to search the "/etc/system" file for a reference to the "c2audit" kernel module: $ grep c2audit /etc/system set c2audit:audit_load = 1 3. Symptoms After logging in to a Solaris 9 system using ssh(1) as a non-root user, the audit-ID of the login shell process will be zero. A command such as the following can be run as either 'root' user or as a user assigned the 'Audit Control' execution profile (see rbac(5)) to determine the audit-ID of a running process on the system: # auditconfig -getpinfo <process ID> | grep 'audit id' audit id = root(0) If the above audit-ID output is seen for a process ID of a non-root user who has logged in via ssh(1), then this issue has occurred on the system. 4. Relief/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 9 with patch 122300-17 or later x86 Platform * Solaris 9 with patch 122301-17 or later Note: The resolution for this issue applies to future audit records. The patches do not modify existing audit records already written to the audit.log(4). For more information on Security Sun Alerts, see Sun Infodoc 91209. 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-2006 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 iQCVAwUBR2nJYCh9+71yA2DNAQIk1AP+K5hhaP7ftlnZrkLeddVxH84Vd67jXSwM CaqtL96xw37e7AUk5QFXs1Oyri6opG4S1EZMaLN0s/A4LCw8Ph4MYlPD6ts1amKf jB1RF20dyLIht6SVMFU8GR7PKn3JAgirF99opjAGctfbBIGzrF2sYeJMLDIBghMl 2W7OKA5eLVo= =+OMi -----END PGP SIGNATURE-----