****************************************************************************** ------ ----- ----- --- ----- | ----- ---- | | | | | |--- | | | | | | | | | |-- | | | | |-- | | | | | | | | \ | | ----- ---- ----- ----- | \ ----- A D V I S O R Y 97.22 ****************************************************************************** Topic: Vulnerability in getopt (3) Source: CIAC Creation Date: June 5, 1997 21:00 GMT Last Updated: To aid in the wide distribution of essential security information, FedCIRC is forwarding the following information from CIAC bulletin H-69. 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 Vulnerability in getopt (3) June 5, 1997 21:00 GMT Number H-69 ______________________________________________________________________________ PROBLEM: A vulnerability has been identified in the getopt (3) function in the libc library. PLATFORM: SunOS versions 5.5.1, 5.5.1_x86, 5.5, 5.5_x86, 5.4, 5.4_x86, and 5.3. DAMAGE: This vulnerability may allow users to cause programs using getopt (3) to execute arbitrary commands. If these programs are setuid or setgid, a user may gain unauthorized root access. SOLUTION: (1) For SunOS 5.5.1, 5.5.1_x86, 5.5, 5.5_x86, or 5.4 apply patches specified below. (2) For SunOS 5.4_x86 or 5.3 apply workarounds specified below until patches for these systems are made available. ______________________________________________________________________________ VULNERABILITY Exploit information for this vulnerability has been ASSESSMENT: made publicly available. ______________________________________________________________________________ [Start Sun Microsystems Advisory] - ------------------------------------------------------------------------------ Sun Microsystems, Inc. Security Bulletin Bulletin Number: #00141 Date: 4 June 1997 Cross-Ref: Title: Vulnerability in getopt(3) - ------------------------------------------------------------------------------ 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, and 2.4 (SunOS 5.5.1, 5.5, and 5.4) that relate to a vulnerability with the getopt(3) function in the libc library. Any privileged program (setuid or setgid) that uses getopt(3) may exploit the vulnerability to gain root access. Sun estimates the release of patches for Solaris 2.4_x86 and 2.3 (SunOS 5.4_x86 and 5.3) that relate to the same vulnerability will be available within 1 week and 3 weeks respectively of the date of this bulletin. Sun strongly recommends that you: a. install the patches listed in section 5 immediately on every system running SunOS 5.5.1, 5.5.1_x86, 5.5, 5.5_x86, or 5.4 b. apply the workarounds specified in section 4 immediately on every system running SunOS 5.4_x86 or 5.3. 2. Who is Affected Vulnerable: SunOS versions 5.5.1, 5.5.1_x86, 5.5, 5.5_x86, 5.4, 5.4_x86, and 5.3. Not vulnerable: All other supported versions of SunOS This vulnerability is fixed in the upcoming release of Solaris. 3. Understanding the Vulnerability The getopt(3) function parses options from a program's command list. Due to insufficient bounds checking by getopt(3) while processing command line arguments, it is possible to overwrite the internal stack space of programs that use getopt(3). This may allow users to cause programs using getopt(3) to execute arbitrary commands by supplying carefully crafted arguments to these programs. If these programs are setuid or setgid, then these commands may be run with those privileges. Any dynamically or statically linked setuid or setgid program that uses getopt(3) may be vulnerable. 4. Workarounds 4.1 Dynamically linked programs The vulnerability can be exploited by using getopt(3) to print error messages when an invalid option is discovered. These messages can be suppressed by setting "opterr" (a global libc variable) to zero by doing the following: As root, execute the following command: # adb -w /lib/libc.so.1 Type the following: opterr?W0 The system will respond with: opterr: 0x1 = 0x0 Type Control-D to exit adb. Note that this workaround will suppress getopt(3) error messages from all dynamically linked executables. 4.2 Statically linked programs The workaround in 4.1 cannot be applied to statically linked setuid or setgid programs. Other than /usr/sbin/static/rcp, Sun is not aware of any other statically linked executable that uses getopt(3). The vulnerability in the rcp program can be closed by removing the setuid bit with a command such as the following: chmod 555 /usr/sbin/static/rcp The rcp program is typically run as root during system boot or recovery only. 5. The vulnerability relating to getopt(3) is fixed by the following patches: OS version Patch ID ---------- -------- SunOS 5.5.1 103612-23 SunOS 5.5.1_x86 103613-23 SunOS 5.5 103187-25 SunOS 5.5_x86 103188-25 SunOS 5.4 101945-49 SunOS 5.4_x86 101946-43 (to be released in 1 week) SunOS 5.3 101318-87 (to be released in 3 weeks) 6. Checksum Table The checksum table below shows the BSD checksums (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: ftp://sunsolve1.sun.com/pub/patches/patches.html These checksums may not apply if you obtain patches from your answer centers. File Name BSD SVR4 MD5 - --------------- --------- --------- -------------------------------- 103612-23.tar.Z 58756 3133 30630 6266 80BFC84479DAED881141250D924C6B1A 103613-23.tar.Z 25868 2829 1295 5657 5AE2770752A17D853029B539EF94B783 103187-25.tar.Z 64511 3195 17448 6389 36120E6EB91C100EB302CE2FEE96739A 103188-25.tar.Z 07195 2880 23176 5760 6707EAB1BD10B845F535E131836F8DC5 101945-49.tar.Z 25995 10899 19660 21798 D67A5744C87BAD1A31D87AED6DC3C362 - ------------------------------------------------------------------------------ Sun acknowledges with thanks AUSCERT, CERT/CC, and DFNCERT for their assistance in the preparation of this bulletin. Sun, AUSCERT, CERT/CC, and DFNCERT are members of FIRST, the Forum of Incident Response and Security Teams. For more information about FIRST, visit the FIRST web site at "http://www.first.org/". - ------------------------------------------------------------------------------ APPENDICES A. Patches listed in this bulletin are available to all Sun customers via World Wide Web at: ftp://sunsolve1.sun.com/pub/patches/patches.html Customers with Sun support contracts can also obtain patches from local Sun answer centers and SunSITEs worldwide. B. 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 C. 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 LIST A list of current security topics QUERY [topic] The mail containing the question is relayed to the Security Coordination Team for response. REPORT [topic] The mail containing the text is treated as a security report and forwarded to the Security Coordination Team. We do not recommend that detailed problem descriptions be sent in plain text. 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 our mailing list. - ------------------------------------------------------------------------------ [End Sun Microsystems Advisory] ______________________________________________________________________________ CIAC wishes to acknowledge the contributions of Sun Microsystems, AUSCERT, CERT/CC and DFNCERT 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-60: Vulnerability in metamail H-61: SGI IRIX df, pset, and eject Buffer Overrun Vulnerabilities H-62: SGI IRIX ordist, login/scheme Buffer Overrun Vulnerability H-63: ftpd Signal Handling Vulnerability H-64: SGI IRIX login LOCKOUT parameter Vulnerability H-65: SGI IRIX rld Security Vulnerability H-66: Vulnerability in suidperl (sperl) H-67: Red Hat Linux X11 Libraries Buffer Overflow H-68: Windows95 Network Password Vulnerability -----BEGIN PGP SIGNATURE----- Version: 4.0 Business Edition iQCVAwUBM6CEwbnzJzdsy3QZAQGuGAP/UqFmmv2Ek8DFVgc4dhD+vHjkLpvjeSpx igY/7pF5HuO4SG945p41wCnP/b9XchXOUgIGpUwekHA3aNbwXRUsnYDCNq/MxILl TvkxVGzcOdtOlZS4oSF/Ol5OOYORCh91ln9eCk5wXC49VbFCv6KrbpQYifwpyq6W XE1b5QhvAlk= =tR2j -----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.