****************************************************************************** ------ ----- ----- --- ----- | ----- ---- | | | | | |--- | | | | | | | | | |-- | | | | |-- | | | | | | | | \ | | ----- ---- ----- ----- | \ ----- A D V I S O R Y 97.56 ****************************************************************************** Topic: SunOS, Solaris libXt Vulnerability, Update to libXt in Bulletin H-51 Source: CIAC Creation Date: August 25, 1997 23:00 GMT Last Updated: To aid in the wide distribution of essential security information, FedCIRC is forwarding the following information from CIAC bulletin H-100. FedCIRC urges you to act on this information as soon as possible. If you have any questions, please contact FedCIRC: Telephone: +1 888 282 0870 Email: fedcirc@fedcirc.gov =======================FORWARDED TEXT STARTS HERE============================ -----BEGIN PGP SIGNED MESSAGE----- [ For Public Release ] __________________________________________________________ The U.S. Department of Energy Computer Incident Advisory Capability ___ __ __ _ ___ / | /_\ / \___ __|__ / \ \___ __________________________________________________________ INFORMATION BULLETIN SunOS, Solaris libXt Vulnerability Update to libXt in Bulletin H-51 August 25, 1997 23:00 GMT Number H-100 ______________________________________________________________________________ PROBLEM: A vulnerability exists for a buffer overflow condition in the Xt library and the file xc/lib/Xt/Error.c. PLATFORM: Solaris 2.5.1, 2.5, 2.4, and 2.3 (SunOS versions 5.5.1, 5.5.1_x86, 5.5, 5.5_x86, 5.4, 5.4_x86, 5.3, 4.1.4, and 4.1.3_U1.) DAMAGE: Allows unauthorized file access possibly gaining root privilege. SOLUTION: Apply patches as listed in Section 4. ______________________________________________________________________________ VULNERABILITY Sun strongly recommends that you install the patches listed in ASSESSMENT: section 4 immediately on systems running SunOS 5.5.1, 5.5, 5.4, 5.3, 4.1.4, and 4.1.3_U1. Exploit information is publicly available. ______________________________________________________________________________ [ Start Sun Microsystems Advisory ] ______________________________________________________________________________ Sun Microsystems, Inc. Security Bulletin Bulletin Number: #00153 Date: August 25, 1997 Cross-Ref: CERT CA-97.11 Title: Vulnerabilities in libXt ______________________________________________________________________________ Permission is granted for the redistribution of this Bulletin, so long as the Bulletin is not edited and is attributed to Sun Microsystems. Portions may also be excerpted for re-use in other security advisories so long as proper attribution is included. Any other use of this information without the express written consent of Sun Microsystems is prohibited. Sun Microsystems expressly disclaims all liability for any misuse of this information by any third party. ______________________________________________________________________________ 1. Bulletins Topics Sun announces the release of patches for Solaris 2.5.1, 2.5, 2.4, 2.3, (SunOS 5.5.1, 5.5, 5.4, 5.3), SunOS 4.1.4, and 4.1.3_U1, which relate to vulnerabilities in libXt. Sun strongly recommends that you install the patches listed in section 4 immediately on systems running SunOS 5.5.1, 5.5, 5.4, 5.3, 4.1.4, and 4.1.3_U1. Exploit information is publicly available. 2. Who is Affected Vulnerable: SunOS versions 5.5.1, 5.5.1_x86, 5.5, 5.5_x86, 5.4, 5.4_x86, 5.3, 4.1.4, and 4.1.3_U1 The vulnerabilities are fixed in Solaris 2.6. 3. Understanding the Vulnerabilities libXt is a library in the X Windows system. There are several buffers in libXt that may be overflowed. The buffer overflow vulnerabilities may be exploited through setuid and setgid programs that link libXt to increase privileges, including root privileges. 4. List of Patches The vulnerabilities in libXt are fixed by the following patches: OS version Patch ID __________ ________ SunOS 5.5.1 104338-02 SunOS 5.5.1_x86 105105-01 SunOS 5.5 104337-02 SunOS 5.5_x86 105104-01 SunOS 5.4 105075-01 SunOS 5.4_x86 105103-01 SunOS 5.3 101429-04 SunOS 4.1.4 100512-05 SunOS 4.1.3_U1 100512-05 5. Checksum Table The checksum table below shows the BSD checksums (SunOS 4.1.x: /bin/sum; SunOS 5.x: /usr/ucb/sum), SVR4 checksums (SunOS 5.x: /usr/bin/sum), and the MD5 digital signatures for the above-mentioned patches that are available from: These checksums may not apply if you obtain patches from your answer centers. File Name BSD SVR4 MD5 _______________ _________ __________ ________________________________ 104338-02.tar.Z 19861 746 5636 1492 5C41779D358B7C3E96A6AFBAD69E26BB 105105-01.tar.Z 60209 652 30450 1303 859659A92DE3CB4FC476F41E30442695 104337-02.tar.Z 07260 740 64023 1480 2F9E1064C17AD040EC45255DFF8DEFE5 105104-01.tar.Z 11186 802 44802 1603 580F3B9FF748E0913322CB431893815C 105075-01.tar.Z 51275 709 63521 1417 8B6A52B62D9092C7061A80AA33BDB4AA 105103-01.tar.Z 20278 619 48559 1238 E1A592FFACAFD2B3A79B2A7C525B24A2 101429-04.tar.Z 35975 991 3045 1981 1EA911E52281DD23856316F49825EABA 100512-05.tar.Z 58168 468 3889 936 9189EFFE254BF48BF68B7C381BB78615 ______________________________________________________________________________ APPENDICES A. Patches listed in this bulletin are available to all Sun customers via World Wide Web at: Customers with Sun support contracts can also obtain patches from local Sun answer centers and SunSITEs worldwide. B. Sun security bulletins are available via World Wide Web at: C. Sun Security Coordination Team's PGP key is available via World Wide Web at: D. To report or inquire about a security problem with Sun software, contact one or more of the following: - Your local Sun answer centers - Your representative computer security response team, such as CERT - Sun Security Coordination Team. Send email to: security-alert@sun.com E. To receive information or subscribe to our CWS (Customer Warning System) mailing list, send email to: security-alert@sun.com with a subject line (not body) containing one of the following commands: Command Information Returned/Action Taken _______ _________________________________ help An explanation of how to get information key Sun Security Coordination Team's PGP key list A list of current security topics query [topic] The email is treated as an inquiry and is forwarded to the Security Coordination Team report [topic] The email is treated as a security report and is forwarded to the Security Coordinaton Team. Please encrypt sensitive mail using Sun Security Coordination Team's PGP key send topic A short status summary or bulletin. For example, to retrieve a Security Bulletin #00138, supply the following in the subject line (not body): send #138 subscribe Sender is added to our mailing list. To subscribe, supply the following in the subject line (not body): subscribe cws your-email-address Note that your-email-address should be substituted by your email address. unsubscribe Sender is removed from the CWS mailing list. ______________________________________________________________________________ [ End Sun Microsystems Advisory ] CIAC wishes to acknowledge the contributions of Sun Microsystems, Inc. for the information contained in this bulletin. ______________________________________________________________________________ CIAC, the Computer Incident Advisory Capability, is the computer security incident response team for the U.S. Department of Energy (DOE) and the emergency backup response team for the National Institutes of Health (NIH). CIAC is located at the Lawrence Livermore National Laboratory in Livermore, California. CIAC is also a founding member of FIRST, the Forum of Incident Response and Security Teams, a global organization established to foster cooperation and coordination among computer security teams worldwide. CIAC services are available to DOE, DOE contractors, and the NIH. CIAC can be contacted at: Voice: +1 510-422-8193 FAX: +1 510-423-8002 STU-III: +1 510-423-2604 E-mail: ciac@llnl.gov For emergencies and off-hour assistance, DOE, DOE contractor sites, and the NIH may contact CIAC 24-hours a day. During off hours (5PM - 8AM PST), call the CIAC voice number 510-422-8193 and leave a message, or call 800-759-7243 (800-SKY-PAGE) to send a Sky Page. CIAC has two Sky Page PIN numbers, the primary PIN number, 8550070, is for the CIAC duty person, and the secondary PIN number, 8550074 is for the CIAC Project Leader. Previous CIAC notices, anti-virus software, and other information are available from the CIAC Computer Security Archive. World Wide Web: http://ciac.llnl.gov/ Anonymous FTP: ciac.llnl.gov (198.128.39.53) Modem access: +1 (510) 423-4753 (28.8K baud) +1 (510) 423-3331 (28.8K baud) CIAC has several self-subscribing mailing lists for electronic publications: 1. CIAC-BULLETIN for Advisories, highest priority - time critical information and Bulletins, important computer security information; 2. CIAC-NOTES for Notes, a collection of computer security articles; 3. SPI-ANNOUNCE for official news about Security Profile Inspector (SPI) software updates, new features, distribution and availability; 4. SPI-NOTES, for discussion of problems and solutions regarding the use of SPI products. Our mailing lists are managed by a public domain software package called Majordomo, which ignores E-mail header subject lines. To subscribe (add yourself) to one of our mailing lists, send the following request as the E-mail message body, substituting ciac-bulletin, ciac-notes, spi-announce OR spi-notes for list-name: E-mail to ciac-listproc@llnl.gov or majordomo@tholia.llnl.gov: subscribe list-name e.g., subscribe ciac-notes You will receive an acknowledgment email immediately with a confirmation that you will need to mail back to the addresses above, as per the instructions in the email. This is a partial protection to make sure you are really the one who asked to be signed up for the list in question. If you include the word 'help' in the body of an email to the above address, it will also send back an information file on how to subscribe/unsubscribe, get past issues of CIAC bulletins via email, etc. PLEASE NOTE: Many users outside of the DOE, ESnet, and NIH computing communities receive CIAC bulletins. If you are not part of these communities, please contact your agency's response team to report incidents. Your agency's team will coordinate with CIAC. The Forum of Incident Response and Security Teams (FIRST) is a world-wide organization. A list of FIRST member organizations and their constituencies can be obtained via WWW at http://www.first.org/. This document was prepared as an account of work sponsored by an agency of the United States Government. Neither the United States Government nor the University of California nor any of their employees, makes any warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial products, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation or favoring by the United States Government or the University of California. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or the University of California, and shall not be used for advertising or product endorsement purposes. LAST 10 CIAC BULLETINS ISSUED (Previous bulletins available from CIAC) H-91: HP-UX Large UID's and GID's Vulnerability H-92: HP-UX X11/Motif Lib & Novell Netware Vulerabilities H-93: SGI IRIX ordist Buffer Overrun Vulnerability H-94: Vulnerability in ps H-95: Vulnerability in x-lock H-96: Vulnerability in Bind H-92a: HP-UX X11/Motif Lib and Novell Netware Vulnerabilities H-97: SGI IRIX ftpd Signal Handling Vulnerability H-98: SunOS automounter Vulnerability H-99: SunOS, Solaris ifconfig ioctls Vulnerability -----BEGIN PGP SIGNATURE----- Version: 4.0 Business Edition iQCVAwUBNANYbrnzJzdsy3QZAQE+igP/Tgk0BmH5iQkmKgRJhbwSm5b44huaEzAY pmRXX8tJvHk+XzudNVRuElSQBrmnbhrTyPT9UbyxlVYQPk/MTF3ITenJ92qKx9Zv Jdi/HDRie8kakeBnD344Y9zBod66N32L81t6mCTEQ13W8fWDNZQ0DliUpcztYuJV nbMyix3+Cgg= =cJG5 -----END PGP SIGNATURE----- ========================FORWARDED TEXT ENDS HERE============================= The National Institute of Standards and Technology (NIST) has established a Federal Computer Incident response Capability (FedCIRC) to assist federal civilians agencies in their incident handling efforts by providing proactive and reactive computer security related services. FedCIRC is a partnership among NIST, the Computer Incident Advisory Capability (CIAC), and the CERT* Coordination Center (CERT/CC). If you believe that your system has been compromised, please contact FedCIRC: Telephone: +1 888 282 0870 Email: fedcirc@fedcirc.gov Web Server: http://www.fedcirc.gov/ * Registered in U.S. Patent and Trademark Office The CERT Coordination Center is part of the Software Engineering Institute. The Software Engineering Institute is sponsored by the U.S. Department of Defense. CIAC, the Computer Incident Advisory Capability, is the computer security incident response team for the U.S. Department of Energy (DOE) and the emergency backup response team for the National Institutes of Health (NIH). CIAC is located at the Lawrence Livermore National Laboratory in Livermore, California. CIAC is also a founding member of FIRST, the Forum of Incident Response and Security Teams, a global organization established to foster cooperation and coordination among computer security teams worldwide. This document was prepared as an account of work sponsored by an agency of the United States Government. Neither the United States Government nor the University of California nor any of their employees, makes any warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial products, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation or favoring by the United States Government or the University of California. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or the University of California, and shall not be used for advertising or product endorsement purposes.