fedcirc.97.25.txt
0f4e721867a55ec0b75a8c8825011f3742a1b2006d250d76ab5c8f8b6332032d
******************************************************************************
------ ----- ----- --- -----
| ----- ---- | | | | |
|--- | | | | | | | |
| |-- | | | | |-- |
| | | | | | | \ |
| ----- ---- ----- ----- | \ -----
A D V I S O R Y
97.25
******************************************************************************
Topic: SunOS eeprom Vulnerability
Source: CIAC
Creation Date: June 25, 1997 16:00 GMT
Last Updated:
To aid in the wide distribution of essential security information, FedCIRC is
forwarding the following information from CIAC bulletin H-72. 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 eeprom Vulnerability
June 25, 1997 16:00 GMT Number H-72
______________________________________________________________________________
PROBLEM: A buffer overflow vulnerability has been identified in the
eeprom program.
PLATFORM: SunOS versions 5.3-5.5.1 (Solaris 2.3-2.5.1) for SPARC only.
DAMAGE: This vulnerability may allow local users to gain root
privileges.
SOLUTION: Apply vendor patches specified in Section 4.
______________________________________________________________________________
VULNERABILITY It is highly recommended that patches be installed immediately.
ASSESSMENT:
______________________________________________________________________________
[ Start Sun Microsystems Advisory ]
- ------------------------------------------------------------------------------
Sun Microsystems, Inc. Security Bulletin
Bulletin Number: #00143
Date: June 24 1997
Cross-Ref:
Title: Vulnerability in eeprom
- ------------------------------------------------------------------------------
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, and 2.3
(SunOS 5.5.1, 5.5, 5.4, and 5.3), that relate to a vulnerability in the
eeprom program.
Sun strongly recommends that you install the patches listed in section 4
immediately on every affected system.
2. Who is Affected
Vulnerable: SunOS versions 5.5.1, 5.5, 5.4, and 5.3 for SPARC
only.
Not vulnerable: All other supported versions of SunOS
The vulnerability is fixed in the upcoming release of Solaris.
3. Understanding the Vulnerability
The eeprom program changes or displays the values of parameters in EEPROM.
The EEPROM (Electrically erasable programmable read-only memory) is a
non-volatile PROM that holds information about the current system
configuration, alternate boot paths, and other information. Due to
insufficient bounds checking on arguments passed to the eeprom program,
it is possible to overwrite the internal stack space of eeprom while it is
executing. Since eeprom has setgid bin permissions, this vulnerability may
allow non-privileged users to gain privileged access, including root
privileges.
4. List of Patches
The vulnerability in eeprom is fixed by the following patches:
OS version Patch ID
---------- --------
SunOS 5.5.1 104795-01
SunOS 5.5 104796-01
SunOS 5.4 104798-01
SunOS 5.3 104797-01
Intel x86 systems do not have the eeprom program and are not
affected by this vulnerability.
5. 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
- --------------- --------- --------- --------------------------------
104795-01.tar.Z 03357 150 64333 300 3004B44BE2742A51A593DE8B76679768
104796-01.tar.Z 12042 150 18119 299 92DA0C5513E191A4C3719B3EFFB1B935
104798-01.tar.Z 40939 166 63088 332 DD89275C55397A97C4B06D1E5037723F
104797-01.tar.Z 59061 165 27937 330 BE97B2DD42A890F4E736A323E3CD8A4A
- ------------------------------------------------------------------------------
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. Sun security bulletins are available via World Wide Web at:
http://sunsolve1.sun.com/sunsolve/secbulletins
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 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-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
H-69: Vulnerability in getopt (3)
H-70: Vulnerability in rpcbind
H-71: Vulnerability in the at(1) program
-----BEGIN PGP SIGNATURE-----
Version: 4.0 Business Edition
iQCVAwUBM7LNarnzJzdsy3QZAQF6qQQAnm0bAW5WhCHZLMSlDjT+ipvQt8NIJS/+
qnaOgAZpJf2dbAVYns0A9BVqskHSfbqKycckc++Qg1k26wPEH3Owy3I+NF++rUD0
m2PC1fb1bZlNyPl5ywKuDxzpdh5kJT3t/Z1gX6nP3luKVfD72V52mTtMOiu2xhMF
DkmJbe/njnE=
=qhyH
-----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.