__________________________________________________________
The U.S. Department of Energy
Computer Incident Advisory Capability
___ __ __ _ ___
/ | /_\ /
\___ __|__ / \ \___
__________________________________________________________
INFORMATION BULLETIN
Buffer Overflow in Sun Solstic AdminSuite Daemon sadmind
December 30, 1999 20:00 GMT Number K-013
______________________________________________________________________________
PROBLEM: A buffer overflow vulnerability has been identified in the
AdminSuite Daemon sadmind.
PLATFORM: SunOS 5.7, 5.7_x86, 5.6, 5.6_x86, 5.5.1, 5.5.1_x86, 5.5,
5.5_x86, and 5.4, 5.4_x86, and 5.3 with AdminSuite installed.
DAMAGE: A buffer overflow could allow an intruder access to root.
SOLUTION: Disable sadmind or apply newly released patches. See Sun's
Advisory below for patch information.
______________________________________________________________________________
VULNERABILITY Risk is high. This vulnerability has been discussed on public
ASSESSMENT: security forums and is being actively exploited.
______________________________________________________________________________
[ The CERT Advisory is followed by the update on December 29, 1999 from
Sun Microsystems ]
[ Start CERT's Advisory ]
CERT Advisory CA-99-16 Buffer Overflow in Sun Solstice AdminSuite Daemon
sadmind
Original release date: December 14, 1999
Last revised: --
Source: CERT/CC
A complete revision history is at the end of this file.
Systems Affected
* Systems that have sadmind installed
I. Description
The sadmind program is installed by default in Solaris 2.5, 2.6, and
7. In Solaris 2.3 and 2.4, sadmind may be installed if the Sun
Solstice Adminsuite packages are installed. The sadmind program is
installed in /usr/sbin. It can be used to coordinate distributed
system administration operations remotely. The sadmind daemon is
started automatically by the inetd daemon whenever a request to
perform a system administration operation is received.
All versions of sadmind are vulnerable to a buffer overflow that can
overwrite the stack pointer within a running sadmind process. Since
sadmind is installed as root, it is possible to execute arbitrary
code with root privileges on a remote machine.
This vulnerability has been discussed in public security forums and is
actively being exploited by intruders.
II. Impact
A remote user may be able to execute arbitrary code with root
privileges on systems running vulnerable versions of sadmind.
III. Solution
Disable sadmind
Remove (or comment) the following line in /etc/inetd.conf:
100232/10 tli rpc/udp wait root /usr/sbin/sadmind sadmind
Even though it will not defend against the attack discussed in this
advisory, it is a good practice to set the security option used to
authenticate requests to a STRONG level, for example:
100232/10 tli rpc/udp wait root /usr/sbin/sadmind sadmind -S 2
If you must use sadmind to perform system administration tasks, we
urge you to use this setting.
Appendix A contains information provided by vendors for this advisory.
We will update the appendix as we receive or develop more information.
If you do not see your vendor's name in Appendix A, the CERT/CC did
not hear from that vendor. Please contact your vendor directly.
Appendix A. Vendor Information
Sun Microsystems
Sun Microsystems is currently working on patches to address the issue
discussed in this advisory and recommends disabling sadmind.
_________________________________________________________________
The CERT Coordination Center thanks Sun Microsystems for its help in
providing information for this advisory.
______________________________________________________________________
This document is available from:
http://www.cert.org/advisories/CA-99-16-sadmind.html
______________________________________________________________________
[ Start Sun's Advisory ]
______________________________________________________________________________
Sun Microsystems, Inc. Security Bulletin
Bulletin Number: #00191
Date: December 29, 1999
Cross-Ref: CERT CA-99-16
Title: sadmind
______________________________________________________________________________
The information contained in this Security Bulletin is provided "AS IS."
Sun makes no warranties of any kind whatsoever with respect to the information
contained in this Security Bulletin. ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY WARRANTY OF NON-INFRINGEMENT OR
IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, ARE
HEREBY DISCLAIMED AND EXCLUDED TO THE EXTENT ALLOWED BY APPLICABLE LAW.
IN NO EVENT WILL SUN MICROSYSTEMS, INC. BE LIABLE FOR ANY LOST REVENUE,
PROFIT OR DATA, OR FOR DIRECT, SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL
OR PUNITIVE DAMAGES HOWEVER CAUSED AND REGARDLESS OF ANY THEORY OF LIABILITY
ARISING OUT OF THE USE OF OR INABILITY TO USE THE INFORMATION CONTAINED IN
THIS SECURITY BULLETIN, EVEN IF SUN MICROSYSTEMS, INC. HAS BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGES.
If any of the above provisions are held to be in violation of applicable law,
void, or unenforceable in any jurisdiction, then such provisions are waived
to the extent necessary for this disclaimer to be otherwise enforceable in
such jurisdiction.
______________________________________________________________________________
1. Bulletins Topics
Sun announces the release of patches for Solaris(tm) 7, 2.6, 2.5.1,
2.5, 2.4, and 2.3 (SunOS(tm) 5.7, 5.6, 5.5.1, 5.5, 5.4 and 5.3), which
relate to a vulnerability with sadmind.
Sun recommends that you install the patches listed in section 4
immediately on systems running SunOS 5.7, 5.6, 5.5.1, and 5.5 and
on systems with Solstice AdminSuite (AdminSuite) installed. If you have
installed a version of AdminSuite prior to version 2.3, please upgrade
to AdminSuite 2.3 before installing the AdminSuite patches listed in
section 4.
Sun also recommends that you:
- disable sadmind if you do not use it by commenting the
following line in /etc/inetd.conf:
100232/10 tli rpc/udp wait root /usr/sbin/sadmind sadmind
- set the security level used to authenticate requests to STRONG
as follows, if you use sadmind:
100232/10 tli rpc/udp wait root /usr/sbin/sadmind sadmind -S 2
The above changes to /etc/inetd.conf will take effect after inetd
receives a hang-up signal.
2. Who is Affected
Vulnerable: SunOS 5.7, 5.7_x86, 5.6, 5.6_x86, 5.5.1, 5.5.1_x86,
5.5, 5.5_x86, and
5.4, 5.4_x86, and 5.3 with AdminSuite installed
Not vulnerable: All other supported versions of SunOS.
3. Understanding the Vulnerability
The sadmind program is installed by default on SunOS 5.7, 5.6, 5.5.1,
and 5.5. In SunOS 5.4 and 5.3, sadmind may be installed if the
Solstice AdminSuite packages are installed. The sadmind program
is installed in /usr/sbin. The program can be used to perform
distributed system administration operations remotely. A buffer overflow
vulnerability has been discovered in sadmind which may be exploited by
a remote attacker to execute arbitrary instructions and gain root access.
4. List of Patches
The following patches are available in relation to the above problem.
OS Version Patch ID
__________ _________
SunOS 5.7 108662-01
SunOS 5.7_x86 108663-01
SunOS 5.6 108660-01
SunOS 5.6_x86 108661-01
SunOS 5.5.1 108658-01
SunOS 5.5.1_x86 108659-01
SunOS 5.5 108656-01
SunOS 5.5_x86 108657-01
AdminSuite Version Patch ID
__________________ ________
2.3 104468-18 (see Note)
2.3_x86 104469-18 (see Note)
Note: Install patch if AdminSuite is installed. AdminSuite may be
installed on SunOS 5.7, 5.6, 5.5.1, 5.5, 5.4 or 5.3.
______________________________________________________________________________
Sun acknowledges, with thanks, Stanford University and the CERT Coordination
Center for their assistance in this matter.
______________________________________________________________________________
APPENDICES
A. Patches listed in this bulletin are available to all Sun customers at:
http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/patch-
license&nav=pub-patches
B. Checksums for the patches listed in this bulletin are available at:
ftp://sunsolve.sun.com/pub/patches/CHECKSUMS
C. Sun security bulletins are available at:
http://sunsolve.sun.com/pub-cgi/secBulletin.pl
D. Sun Security Coordination Team's PGP key is available at:
http://sunsolve.sun.com/pgpkey.txt
E. 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
F. 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 Coordination 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.
______________________________________________________________________________
Copyright 1999 Sun Microsystems, Inc. All rights reserved. Sun,
Sun Microsystems, Solaris and SunOS are trademarks or registered trademarks
of Sun Microsystems, Inc. in the United States and other countries. This
Security Bulletin may be reproduced and distributed, provided that this
Security Bulletin is not modified in any way and is attributed to
Sun Microsystems, Inc. and provided that such reproduction and distribution
is performed for non-commercial purposes.
[ End Advisories ]
______________________________________________________________________________
CIAC wishes to acknowledge the contributions of CERT and Sun Microsystems 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 925-422-8193
FAX: +1 925-423-8002
STU-III: +1 925-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), use one of the following methods to contact CIAC:
1. Call the CIAC voice number 925-422-8193 and leave a message, or
2. Call 888-449-8369 to send a Sky Page to the CIAC duty person or
3. Send e-mail to 4498369@skytel.com, or
4. Call 800-201-9288 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://www.ciac.org/
(or http://ciac.llnl.gov -- they're the same machine)
Anonymous FTP: ftp.ciac.org
(or ciac.llnl.gov -- they're the same machine)
Modem access: +1 (925) 423-4753 (28.8K baud)
+1 (925) 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. SPI-ANNOUNCE for official news about Security Profile Inspector
(SPI) software updates, new features, distribution and
availability;
3. 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, spi-announce OR spi-notes for list-name:
E-mail to ciac-listproc@llnl.gov or majordomo@rumpole.llnl.gov:
subscribe list-name
e.g., subscribe ciac-bulletin
You will receive an acknowledgment E-mail immediately with a confirmation
that you will need to mail back to the addresses above, as per the
instructions in the E-mail. 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 E-mail to the above address,
it will also send back an information file on how to subscribe/unsubscribe,
get past issues of CIAC bulletins via E-mail, 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)
K-003: Windows NT 4.0 does not delete Unattended Installation File
K-004: Microsoft "Excel SYLK" Vulnerability
K-005: Microsoft "Virtual Machine Verifier" Vulnerability
K-006: Microsoft - Improve TCP Initial Sequence Number Randomness
K-007: Multiple Vulnerabilities in BIND
K-008: ExploreZip (packed) Worm
K-009: Qpopper Buffer Overflow Vulnerability
K-010: Solaris Snoop Buffer Overflow Vulnerability
K-011: Buffer Overflow Vulnerabilities in SSH Daemon and RSAREF2
K-012: Cisco Cache Engine Authentication Vulnerabilities
TUCoPS is optimized to look best in Firefox® on a widescreen monitor (1440x900 or better).
Site design & layout copyright © 1986-2024 AOH
