Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 =========================================================================== AUSCERT External Security Bulletin Redistribution ESB-2007.0626 -- [Solaris] Two Security Vulnerabilities in Solaris 8 Role Based Access Control (rbac(5)) may Allow Unauthorized Remote Access 20 August 2007 =========================================================================== AusCERT Security Bulletin Summary --------------------------------- Product: Role Based Access Control (RBAC) Publisher: Sun Microsystems Operating System: Solaris 8 Impact: Root Compromise Inappropriate Access Access: Existing Account Original Bulletin: http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-26-103029-1 - --------------------------BEGIN INCLUDED TEXT-------------------- Sun(sm) Alert Notification * Sun Alert ID: 103029 * Synopsis: Two Security Vulnerabilities in Solaris 8 Role Based Access Control (rbac(5)) may Allow Unauthorized Remote Access * Category: Security * Product: Solaris 8 Operating System * BugIDs: 4625194, 4418892 * Avoidance: Patch, Workaround * State: Resolved * Date Released: 16-Aug-2007 * Date Closed: 16-Aug-2007 * Date Modified: 1. Impact Two security vulnerabilities in the Solaris 8 Role Based Access Control (RBAC) mechanism on hosts on which RBAC roles (see rbac(5)) have been created may allow a remote user who knows the passwords for certain roles to gain unauthorized access to the system via the role accounts. If the root user has been assigned a role, a remote user who knows the password for that role may gain unauthorized root privileges on the system. 2. Contributing Factors This issues can occur in the following releases: SPARC Platform * Solaris 8 without patch 127033-01 x86 Platform * Solaris 8 without patch 127034-01 Note 1: Solaris 9 and Solaris 10 are not impacted by this issue. Note 2: Solaris 8 hosts on which RBAC roles have been created are affected by the issue that allows unauthorized remote access via the role accounts. Roles are configured in the user_attr(4) database. If the host is configured to only use a local file for this database, a command such as the following can be used to determine if any roles have been created on the system: $ grep type=role /etc/user_attr testrole::::type=role For hosts which are configured via nsswitch.conf(4) to use a source other than a local file for the user_attr(4) database, please refer to the relevant documentation for that source (for example, ldap(1), ypfiles(4) or nis+(1)). If the root user has any roles assigned, it may be possible to gain root privileges on the host by knowing the passwords for those role accounts. The following command may be executed to see if the root user has been assigned any roles: $ roles root roles: root : No roles 3. Symptoms If the described issues are exploited, output from commands such as last(1) (which display information about login and logout activity), may show logins to roles assigned to the users on the system. Using the "-a" flag with the last(1) command will show the hostname associated with these logins. 4. Relief/Workaround To work around the issue that allows unauthorized remote root access, remove all rbac(5) roles assigned to the root user. This may be done by executing the following command as the root user: # usermod -R "" root To prevent unauthorized access to the system via the role accounts, the role accounts can be removed from the system using a command such as the following: # userdel role_name Note: This will also disable legitimate access to those role accounts until they are recreated. 5. Resolution This issue is addressed in the following releases: SPARC Platform * Solaris 8 with patch 127033-01 or later x86 Platform * Solaris 8 with patch 127034-01 or later 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 iQCVAwUBRsjuBSh9+71yA2DNAQKF8wP/Xm62xFdWkwE3usVcYxyElBaiYu0hGu7m 9R7DK3Hkd9WLuY1fmogDF+IWDaIXRRhZodMBwVVPrEtrRD/1NGfonEvu7lTB8pvU ZYpldcYmiqBApwt2y3bs+nvWL75IGWrgzr/Ck98DH8bYm18k80BKL3d9Q2db2s5l vDnvutCUDs4= =vlIZ -----END PGP SIGNATURE-----