From agent99@csd.sgi.com Mon Sep 11 11:56:06 2000 From: SGI Security Coordinator Resent-From: mea culpa To: agent99@sgi.com Resent-To: jericho@attrition.org Date: Wed, 6 Sep 2000 13:01:41 -0700 (PDT) Subject: IRIX telnetd vulnerability -----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SGI Security Advisory Title: IRIX telnetd vulnerability Number: 20000801-01-P Date: September 6, 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 Last Stage of Delirium Group (http://lsd-pl.net/) has reported via BUGTRAQ that an exploitable buffer overflow has been discovered in telnetd daemon which can lead to a root compromise. 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 will be corrected in future releases of IRIX. - -------------- - --- Impact --- - -------------- The telnetd daemon is installed by default on IRIX. A local user account on the vulnerable system is not required in order to exploit telnetd daemon. The telnetd daemon can be exploited remotely over an untrusted network. The exploitable buffer overflow vulnerability can lead to a root compromise. This telnetd buffer overflow vulnerability was reported by LSD on BUGTRAQ: http://msgs.securepoint.com/cgi-bin/get/bugtraq0008/152.html http://lsd-pl.net/files/get?IRIX/irx_telnetd This telnetd vulnerability has been publicly discussed in Usenet newsgroups and mailing lists. - -------------------------- - --- 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 telnetd daemon to prevent exploitation of this vulnerability until patches can be installed. ================ **** NOTE **** ================ Disabling telnetd daemon will disable the telnet service. 1) Become the root user on the system. % /bin/su - Password: # 2) Edit the file /etc/inetd.conf (for IRIX 5.3 and lower, edit /usr/etc/inetd.conf) with your favorite text editor. Place a "#" as the first character of the line to comment out and deactivate the telnetd daemon. # vi /etc/inetd.conf {Find the following line} telnet stream tcp nowait root /usr/etc/telnetd telnetd {Place a "#" as the first character of the telnet line} #telnet stream tcp nowait root /usr/etc/telnetd telnetd {Save the file} 3) Force inetd to re-read the configuration file. # /etc/killall -HUP inetd 4) Kill any existing telnetd process. # /etc/killall telnetd 5) Return to previous level. # exit % - ---------------- - --- Solution --- - ---------------- OS Version Vulnerable? Patch # Other Actions ---------- ----------- ------- ------------- IRIX 3.x unknown Note 1 IRIX 4.x unknown Note 1 IRIX 5.0.x unknown Note 1 IRIX 5.1.x unknown Note 1 IRIX 5.2 yes not avail Note 1 & 3 IRIX 5.3 yes in progress Note 1 & 3 IRIX 6.0.x yes not avail Note 1 & 3 IRIX 6.1 yes not avail Note 1 & 3 IRIX 6.2 yes 4050 Note 2 & 3 IRIX 6.3 yes in progress Note 1 IRIX 6.4 yes in progress Note 1 IRIX 6.5 yes 4044 Note 3 & 4 IRIX 6.5.1 yes 4044 Note 3 & 4 IRIX 6.5.2 yes 4044 Note 3 & 4 IRIX 6.5.3 yes 4044 Note 3 & 4 IRIX 6.5.4 yes 4044 Note 3 & 4 IRIX 6.5.5 yes 4044 Note 3 & 4 IRIX 6.5.6 yes 4044 Note 3 & 4 IRIX 6.5.7 yes 4044 Note 3 & 4 IRIX 6.5.8 yes 4044 Note 3 & 4 IRIX 6.5.9 yes 4044 Note 3 & 4 IRIX 6.5.10 no Note 4 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. 4) If you have not received an IRIX 6.5.X CD for IRIX 6.5, contact your SGI Support Provider or download the IRIX 6.5.X Maintenance Release Stream from http://support.sgi.com/ or ftp://patches.sgi.com/support/relstream/ Patches are available via the web, anonymous FTP and from your SGI service/support provider. SGI patches for IRIX can be found at: http://support.sgi.com/irix/ and ftp://patches.sgi.com/ SGI patches and RPMs for Linux can be found at: http://support.sgi.com/linux/ and click on patches link and http://oss.sgi.com/projects/sgilinux-combined/download/security-fixes/ SGI patches for Windows NT or 2000 can be found at: http://support.sgi.com/nt/ IRIX 5.2-6.4 Recommended/Required Patch Sets can be found at: http://support.sgi.com/irix/ and ftp://patches.sgi.com/support/patchset/ IRIX 6.5 Maintenance Release Streams can be found at: http://support.sgi.com/irix/ and ftp://patches.sgi.com/support/relstream/ SGI Security Advisories can be found at: http://www.sgi.com/support/security/ and ftp://sgigate.sgi.com/security/ SGI Security Patches 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.4044 Algorithm #1 (sum -r): 60759 8 README.patch.4044 Algorithm #2 (sum): 27639 8 README.patch.4044 MD5 checksum: EEA022CD7965F3E7A3B7507F7EB408D9 Filename: patchSG0004044 Algorithm #1 (sum -r): 51699 3 patchSG0004044 Algorithm #2 (sum): 35763 3 patchSG0004044 MD5 checksum: B1C88A8AC2AD2A1C2A615BABFB5462C9 Filename: patchSG0004044.eoe_sw Algorithm #1 (sum -r): 21346 58 patchSG0004044.eoe_sw Algorithm #2 (sum): 3477 58 patchSG0004044.eoe_sw MD5 checksum: D3810601399BCA7E3140F93418C16937 Filename: patchSG0004044.idb Algorithm #1 (sum -r): 62780 2 patchSG0004044.idb Algorithm #2 (sum): 43138 2 patchSG0004044.idb MD5 checksum: 9897A6ADBD25EF6FE306C11C4C9CA436 Filename: README.patch.4050 Algorithm #1 (sum -r): 09695 31 README.patch.4050 Algorithm #2 (sum): 11029 31 README.patch.4050 MD5 checksum: 46670A77C1434CE35161779AEA0A9348 Filename: patchSG0004050 Algorithm #1 (sum -r): 29875 17 patchSG0004050 Algorithm #2 (sum): 63516 17 patchSG0004050 MD5 checksum: C40B2DE50608C0A6C79C2167116FF76E Filename: patchSG0004050.eoe_man Algorithm #1 (sum -r): 60740 74 patchSG0004050.eoe_man Algorithm #2 (sum): 15611 74 patchSG0004050.eoe_man MD5 checksum: C45B59724AC5F81F5960BE78104A6B9E Filename: patchSG0004050.eoe_sw Algorithm #1 (sum -r): 47453 1976 patchSG0004050.eoe_sw Algorithm #2 (sum): 46187 1976 patchSG0004050.eoe_sw MD5 checksum: 1D9727E9EAC3F52D56F2EC7F481D5C73 Filename: patchSG0004050.eoe_sw64 Algorithm #1 (sum -r): 49580 104 patchSG0004050.eoe_sw64 Algorithm #2 (sum): 38983 104 patchSG0004050.eoe_sw64 MD5 checksum: 65A02D0562E0F41752363927E3CBC7F4 Filename: patchSG0004050.idb Algorithm #1 (sum -r): 55544 16 patchSG0004050.idb Algorithm #2 (sum): 31605 16 patchSG0004050.idb MD5 checksum: 143E7D4B9E38E604A4F35D504FCAFF28 Filename: patchSG0004050.netman_data_man Algorithm #1 (sum -r): 56900 15 patchSG0004050.netman_data_man Algorithm #2 (sum): 58999 15 patchSG0004050.netman_data_man MD5 checksum: 42BEB35E700813967F637E9BB0640385 Filename: patchSG0004050.nfs_man Algorithm #1 (sum -r): 05186 17 patchSG0004050.nfs_man Algorithm #2 (sum): 21113 17 patchSG0004050.nfs_man MD5 checksum: F090E7476C01DC64F12F3A094EFAD64B Filename: patchSG0004050.nfs_sw Algorithm #1 (sum -r): 48229 83 patchSG0004050.nfs_sw Algorithm #2 (sum): 63547 83 patchSG0004050.nfs_sw MD5 checksum: 093B835EDC966A30980D914149BED1F0 - ------------------------ - --- Acknowledgments ---- - ------------------------ SGI wishes to thank the users of the Internet Community at large 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 end ^d In the example above, 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 iQCVAwUBObafC7Q4cFApAP75AQEKCgP+OaJ/xVFCkdkjAolGL1YclxMkStNJ3WD3 Bx9QC+0cweO9RIyyLyQZ9REPzhDGsiZl48wD6bmLL1EO4/qIDMpAtOs0EXoI8UbQ ybw+cFsnKt/yH1OtRLYow+cADVE+DKHbR/Q0AtNfFRiOauLgd2i56zdyUWDyifeb PcSnPNly3wE= =JoOy -----END PGP SIGNATURE-----