******************************************************************************
------ ----- ----- --- -----
| ----- ---- | | | | |
|--- | | | | | | | |
| |-- | | | | |-- |
| | | | | | | \ |
| ----- ---- ----- ----- | \ -----
A D V I S O R Y
FA-97.39
******************************************************************************
Topic: Solaris ping Vulnerability
Source: CIAC
Creation Date: July 16, 1997
Last Updated:--
To aid in the wide distribution of essential security information, FedCIRC is
forwarding the following information from CIAC bulletin H-83. 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
Solaris ping Vulnerability
Revision to Denial-of-Service Attack via ping in Bulletin H-18
July 16, 1997 20:00 GMT Number H-83
______________________________________________________________________________
PROBLEM: A vulnerability exists with specific ICMP ECHO_REQUEST (ping)
packet.
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 makes it possible for an external user to
cause a system abort.
SOLUTION: Apply patches or workaround listed below.
______________________________________________________________________________
VULNERABILITY Sun strongly recommends that you install the patches or
ASSESSMENT: workaround immediately. Exploit information is publicly
available.
______________________________________________________________________________
[ Start Sun Microsystems, Inc. Security Bulletin ]
______________________________________________________________________________
Sun Microsystems, Inc. Security Bulletin
Bulletin Number: #00146
Date: July 15, 1997
Cross-Ref:
Title: Vulnerability in ping
______________________________________________________________________________
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 and 2.5
(SunOS 5.5.1 and 5.5), which relate to a vulnerability in the
IP driver via the ping utility.
Sun estimates that the release of patches for Solaris 2.4 and 2.3
(SunOS 5.4 and 5.3) which relate to the same vulnerability will be
available within 8 weeks and 16 weeks respectively of the date
of this bulletin.
Sun strongly recommends that you install the patches listed in
section 5 immediately on systems running SunOS 5.5.1 and 5.5. Sun
also strongly recommends that you install the workaround listed in
section 4 immediately on systems running SunOS 5.4 or 5.3. 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, and 5.3.
Not vulnerable: All other supported versions of SunOS
The vulnerability is fixed in the upcoming release of Solaris.
3. Understanding the Vulnerability
The ping program uses the ICMP protocol's ECHO_REQUEST datagram to elicit
an ICMP ECHO_RESPONSE from specified hosts. The vulnerability entails
sending a ping request to a multicast address through the loopback
interface. Part of the effect is that the system pings itself. However,
the incoming queue pointer is not yet initialized when the packet is
received causing the system to panic. The fix, as delivered via the
patches mentioned in section 5, is to initialize the queue pointer to
the correct queue at the time the packet is received.
4. Workaround
Sun recommends as a temporary workaround that all systems be protected
by executing the following command as root:
/usr/sbin/ndd -set /dev/ip ip_respond_to_echo_broadcast 0
Adding the above command to the file /etc/init.d/inetinit makes the
workaround effective across reboots.
5. List of Patches
The vulnerability in ping is fixed by the following patches:
OS version Patch ID
__________ ________
SunOS 5.5.1 103630-09
SunOS 5.5.1_x86 103631-09
SunOS 5.5 103169-12
SunOS 5.5_x86 103170-12
SunOS 5.4 101945-52 (to be released in 8 weeks)
SunOS 5.4_x86 101946-46 (to be released in 8 weeks)
SunOS 5.3 101318-89 (to be released in 16 weeks)
6. Checksum Table
The checksum table below shows 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:
These checksums may not apply if you obtain patches from your answer
centers.
File Name BSD SVR4 MD5
_______________ _________ __________ ________________________________
103630-09.tar.Z 48744 656 23098 1311 BF33542DAD2C1455C6B94300E65B7447
103631-09.tar.Z 10984 573 53999 1145 B8CF75F23D243F9A8947A8FA05CC82BE
103169-12.tar.Z 62974 650 32631 1299 651D2F25A65FDA49FCED0C68CBD7EA32
103170-12.tar.Z 54167 568 15267 1135 9C31DCECA19A8AB621A11B13B4F80986
_____________________________________________________________________________
Sun acknowledges, with thanks, Mark Henderson for providing the workaround
referenced in this bulletin.
_____________________________________________________________________________
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. 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
D. 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, Inc. Security Bulletin ]
______________________________________________________________________________
CIAC wishes to acknowledge the contributions of Sun Microsystems, Inc. and
Mark Henderson 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-74: Unix lpr Buffer Overrun Vulnerability
H-75: Solaris Solstice AdminSuite Vulnerabilities
H-76: Netscape Navigator Security Vulnerability
H-77: Microsoft IIS Boundary Condition Vulnerability
H-78: ICMP vulnerability in Windows 95 and NT 4.0
H-79: Vellum 3D CD-ROM contains Mac MBDF Virus
H-80: SGI IRIX xlock Vulnerability
H-42a: HP MPE/iX with ICMP Echo Request (ping) Vulnerability
H-81: HP-UX swinstall command in SD-UX Vulnerability
H-82: Lynx Temporary Files & Downloading Vulnerabilities
-----BEGIN PGP SIGNATURE-----
Version: 4.0 Business Edition
iQCVAwUBM81alLnzJzdsy3QZAQGAGQP9HKHu/u0LWvRm2RRYbXazCEj2YxxMSet1
ftwAA9HmtVBZ6LFAhjfMRymT0CSmU+RI0mUdgLDSCsHhlONYipkVvt0lz5IzJXf+
74qihNPU6eTTJ8yaY2C5wkg0hlmTA4rTgG/4cakrncda7N86S29sBY4MuI8HqWxp
HX7vZqBkaKE=
=WkMp
-----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.