|
PROBLEM: A vulnerability exists in the objectserver daemon that may lead to the creation of non-privileged user accounts. PLATFORM: IRIX versions 5.3 and 6.2. IRIX versions 5.0.x, 5.1.x, 5.2, 6.0.x, and 6.1 have not been tested and should be considered vulnerable. DAMAGE: Non-privileged user accounts may be created on a system. A local user account does not need to exist to accomplish this exploit. This vulnerability may also be exploited remotely. SOLUTION: Load the patches specified for IRIX 5.3 and 6.2. For IRIX 5.0.x, 5.1.x, 5.2, 6.0.x, and 6.1 follow the instructions in the "Temporary Solution" section.
VULNERABILITY The risk is high. This exploit has been discussed in public ASSESSMENT: forums.
[****** Begin SGI Security Advisory ******] -----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SGI Security Advisory Title: Vulnerability in IRIX 5.3 and 6.2 objectserver Number: 20000303-01-PX Date: March 28, 2000 ______________________________________________________________________________ SGI provides this information freely to the SGI user community for its consideration, interpretation, implementation and use. SGI recommends that this information be acted upon as soon as possible. SGI provides the information in this Security Advisory on an "AS-IS" basis only, and disclaims all warranties with respect thereto, express, implied or otherwise, including, without limitation, any warranty of merchantability or fitness for a particular purpose. In no event shall SGI be liable for any loss of profits, loss of business, loss of data or for any indirect, special, exemplary, incidental or consequential damages of any kind arising from your use of, failure to use or improper use of any of the instructions or information in this Security Advisory. ______________________________________________________________________________ - ----------------------- - --- Issue Specifics --- - ----------------------- The objectserver(1M) daemon manages Cadmin objects like disks, tapes and user accounts. Cadmin(1M) applications like cpeople(1) use the objectserver to add, remove or modify user accounts. Unfortunately, a vulnerability in the objectserver(1M) daemon has been discovered which can lead to unauthorized non-privileged user accounts being created. SGI has investigated the issue and recommends the following steps for neutralizing the exposure. It is HIGHLY RECOMMENDED that these measures be implemented on ALL vulnerable SGI systems. This issue has been corrected in future releases of IRIX. - -------------- - --- Impact --- - -------------- The objectserver(1M) daemon is installed by default on all IRIX operating systems versions 5.1 through 6.2. The Cadmin system administration tools were replaced with the new "IRIX Interactive Desktop System Administration" or sysmgr(1M) as of IRIX 6.3 and above. This new suite of tools does not use the objectserver daemon and therefore is not vulnerable to this issue. A local user account is not needed in order to accomplish the exploit. The vulnerability can be exploited remotely to create non-privileged user accounts. It is believed that this vulnerability in objectserver daemon has been publicly discussed in limited forums. - -------------------------- - --- Temporary Solution --- - -------------------------- Although patches are available for this issue, it is realized that there may be situations where installing the patches immediately may not be possible. The steps below can be used to disable the objectserver(1M) daemon to prevent exploitation of this vulnerability until patches can be installed. ================= **** WARNING **** ================= Disabling the objectserver daemon will disable the Cadmin system administration tools. 1) Become the root user on the system. % /bin/su - Password: # 2) Prevent the objectserver daemon from starting during boot up. # /sbin/chkconfig objectserver off 3) Kill any running objectserver daemon. # /etc/init.d/cadmin stop; /etc/init.d/cadmin start 4) Return to previous level. # exit % - ---------------- - --- Solution --- - ---------------- OS Version Vulnerable? Patch # Other Actions ---------- ----------- ------- ------------- IRIX 3.x no Note 1 IRIX 4.x no Note 1 IRIX 5.0.x not tested Note 1 & 3 IRIX 5.1.x not tested Note 1 & 3 IRIX 5.2 not tested Note 1 & 3 IRIX 5.3 yes 3654 Note 1 & 3 IRIX 6.0.x not tested Note 1 & 3 IRIX 6.1 not tested Note 1 & 3 IRIX 6.2 yes 2849 Note 2 & 3 IRIX 6.3 no Note 1 IRIX 6.4 no Note 1 IRIX 6.5.X no NOTES 1) This version of the IRIX operating has been retired. Upgrade to an actively supported IRIX operating system. See http://support.sgi.com/irix/news/index.html#policy for more information. 2) This version of the IRIX operating system is in maintenance mode. Upgrade to an actively supported IRIX operating system. See http://support.sgi.com/irix/news/index.html#policy for more information. 3) See "Temporary Solution" section. Patches are available via the web, anonymous FTP and from your SGI service/support provider. IRIX 5.2-6.4 Recommended/Required Patch Sets can be found at: http://support.sgi.com/ and ftp://patches.sgi.com/support/patchset/ IRIX 6.5 Maintenance Release Streams can be found at: http://support.sgi.com/ and ftp://patches.sgi.com/support/relstream/ IRIX Security Patchsets can be found at: http://www.sgi.com/Support/security/ and ftp://sgigate.sgi.com/patches/ The primary SGI anonymous FTP site for security information and patches is sgigate.sgi.com (204.94.209.1). Security information and patches can be found in the ~ftp/security and ~ftp/patches directories, respectively. For security and patch management reasons, ftp.sgi.com (mirror of sgigate) lags behind and does not do a real-time update of ~ftp/security and ~ftp/patches. ##### Patch File Checksums #### The actual patch will be a tar file containing the following files: Filename: README.patch.3654 Algorithm #1 (sum -r): 27220 15 README.patch.3654 Algorithm #2 (sum): 4882 15 README.patch.3654 MD5 checksum: 97B310927A815099930075777E45F0AB Filename: patchSG0003654 Algorithm #1 (sum -r): 13216 11 patchSG0003654 Algorithm #2 (sum): 42485 11 patchSG0003654 MD5 checksum: CF4F3CA358644BBD6F36DC2F0C91B9C8 Filename: patchSG0003654.cadmin_man Algorithm #1 (sum -r): 54103 7 patchSG0003654.cadmin_man Algorithm #2 (sum): 16960 7 patchSG0003654.cadmin_man MD5 checksum: 594C00039327C1762A9F5A2D1720EF0A Filename: patchSG0003654.cadmin_sw Algorithm #1 (sum -r): 15104 1074 patchSG0003654.cadmin_sw Algorithm #2 (sum): 39843 1074 patchSG0003654.cadmin_sw MD5 checksum: 774EEE90311849A0084AFC254332E04A Filename: patchSG0003654.eoe1_man Algorithm #1 (sum -r): 24451 12 patchSG0003654.eoe1_man Algorithm #2 (sum): 4655 12 patchSG0003654.eoe1_man MD5 checksum: 7B690D29231DD4401845369CF88B080E Filename: patchSG0003654.eoe1_sw Algorithm #1 (sum -r): 07943 6 patchSG0003654.eoe1_sw Algorithm #2 (sum): 58262 6 patchSG0003654.eoe1_sw MD5 checksum: D13FA81DF060BE27DA6F0478CA4D0476 Filename: patchSG0003654.eoe2_sw Algorithm #1 (sum -r): 45591 135 patchSG0003654.eoe2_sw Algorithm #2 (sum): 49343 135 patchSG0003654.eoe2_sw MD5 checksum: 49F553F9DEFC8F92AEC00ECFEB5CABE6 Filename: patchSG0003654.idb Algorithm #1 (sum -r): 64120 4 patchSG0003654.idb Algorithm #2 (sum): 33224 4 patchSG0003654.idb MD5 checksum: 865C1DEB578E9263BC9ACF7A7F986E34 Filename: README.patch.2849 Algorithm #1 (sum -r): 58617 11 README.patch.2849 Algorithm #2 (sum): 56244 11 README.patch.2849 MD5 checksum: AAED31676F184DDC39360AF8E3494246 Filename: patchSG0002849 Algorithm #1 (sum -r): 25053 3 patchSG0002849 Algorithm #2 (sum): 34738 3 patchSG0002849 MD5 checksum: 97A1CF82E5229C45C40FA24D08707640 Filename: patchSG0002849.cadmin_man Algorithm #1 (sum -r): 12331 15 patchSG0002849.cadmin_man Algorithm #2 (sum): 61762 15 patchSG0002849.cadmin_man MD5 checksum: ED8E55A93BEEFBB1639C41310622329F Filename: patchSG0002849.cadmin_sw Algorithm #1 (sum -r): 02890 1076 patchSG0002849.cadmin_sw Algorithm #2 (sum): 41534 1076 patchSG0002849.cadmin_sw MD5 checksum: 3B7F7C508F2D0FB744006AFCD37E34D6 Filename: patchSG0002849.idb Algorithm #1 (sum -r): 31363 2 patchSG0002849.idb Algorithm #2 (sum): 18526 2 patchSG0002849.idb MD5 checksum: 20BE7747F40CAE11C34621CC3D128678 - ------------------------ - --- Acknowledgments ---- - ------------------------ SGI wishes to thank the CERT Coordination Center, US Army, MIT Security Group and the University of Chicago Network Security Center for their assistance in this matter. - ----------------------------------------- - --- SGI Security Information/Contacts --- - ----------------------------------------- If there are questions about this document, email can be sent to cse-security-alert@sgi.com. ------oOo------ SGI provides security information and patches for use by the entire SGI community. This information is freely available to any person needing the information and is available via anonymous FTP and the Web. The primary SGI anonymous FTP site for security information and patches is sgigate.sgi.com (204.94.209.1). Security information and patches are located under the directories ~ftp/security and ~ftp/patches, respectively. The SGI Security Headquarters Web page is accessible at the URL: http://www.sgi.com/support/security/ For issues with the patches on the FTP sites, email can be sent to cse-security-alert@sgi.com. For assistance obtaining or working with security patches, please contact your SGI support provider. ------oOo------ SGI provides a free security mailing list service called wiretap and encourages interested parties to self-subscribe to receive (via email) all SGI Security Advisories when they are released. Subscribing to the mailing list can be done via the Web http://www.sgi.com/support/security/wiretap.html or by sending email to SGI as outlined below. % mail wiretap-request@sgi.com subscribe wiretap <YourEmailAddress> end ^d In the example above, <YourEmailAddress> is the email address that you wish the mailing list information sent to. The word end must be on a separate line to indicate the end of the body of the message. The control-d (^d) is used to indicate to the mail program that you are finished composing the mail message. ------oOo------ SGI provides a comprehensive customer World Wide Web site. This site is located at http://www.sgi.com/support/security/ . ------oOo------ For reporting *NEW* SGI security issues, email can be sent to security-alert@sgi.com or contact your SGI support provider. A support contract is not required for submitting a security report. ______________________________________________________________________________ This information is provided freely to all interested parties and may be redistributed provided that it is not altered in any way, SGI is appropriately credited and the document retains and includes its valid PGP signature. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBOOEpq7Q4cFApAP75AQH5HQQAq7s4q6G0LzopU1lu5ZmsnuM4/bYvroai tM3OwLR9jfXgPHxH7+O1XvvL961scesg76gxX4n5IhRLXbXqrY8Xx1pa5t1H/nUE 9sHO9L0EWU2wQlOvW5ddEaEbCUmMrnWCVRnz8pBVkbzNPnZp8jaSIxqzM1eTXuyb NRZsHmLmI18= =QVO1 -----END PGP SIGNATURE----- [****** End SGI Security Advisory ******]
Voice: +1 925-422-8193 (7 x 24) FAX: +1 925-423-8002 STU-III: +1 925-423-2604 E-mail: ciac@llnl.gov World Wide Web: http://www.ciac.org/ http://ciac.llnl.gov (same machine -- either one will work) Anonymous FTP: ftp.ciac.org ciac.llnl.gov (same machine -- either one will work)