Original issue date: March 21, 1994<BR>
Last revised: September 19, 1997<BR>
updated copyright statement
<P>A complete revision history is at the end of this file.
<P>The CERT Coordination Center has received information concerning a
vulnerability that exists on systems where the file /etc/utmp is writable
by any user on the system.
<P>This vulnerability is being actively exploited; please review <A HREF="http://www.cert.org/advisories/CA-94.01.ongoing.network.monitoring.attacks.html">CA-94.01 Ongoing Network Monitoring Attacks</A>.
<P>The problem is known to affect Sun Microsystems, Inc. SunOS 4.1.X and
Solaris 1.1.1 operating systems. Solbourne Computer, Inc. and other Sparc
products using SunOS 4.1.X or Solaris 1.1.1 are also affected. Solaris 2.x
and SunOS 4.1.3_U1 (Solaris 1.1.1) are not affected by this problem.
<P>Patches can be obtained from Sun Answer Centers worldwide. They are also
available via anonymous FTP from ftp.uu.net in the /systems/sun/sun-dist
directory, and in Europe from ftp.eu.net in the /sun/fixes directory.
<P>We queried several vendors in addition to Sun. The following vendors
reported that their operating systems, as distributed by the vendor, are
not affected by this problem:
<P>Convex Computer Corporation <BR>
Digital Equipment Corporation
<BR>Data General Corporation <BR>
Hewlett-Packard Company
IBM<BR>
Intergraph<BR>
Motorola, Inc.<BR> NeXT, Inc.<BR>
Pyramid Technology Corporation<BR>
Sequent Computer Systems
<BR>Sony Corporation
<P>Currently, we are not aware of /etc/utmp being writable on other systems.
If your operating system is not explicitly mentioned above, and if you
determine that /etc/utmp is writable by someone other than root, we
encourage you to contact your vendor.
<P>If /etc/utmp on your system is writable only by the root account, you need
not be concerned about the vulnerability.
<P>We recommend that sites check their /etc/utmp file to be sure it is not
writable by users other than root. If it is generally writable, you should
obtain patches from the system vendor or protect /etc/utmp as described below.
<P><HR>
<H2>I. Description</H2>
If the file /etc/utmp is writable by users other than root,
programs that trust the information stored in that file can
be subverted.
<H2>II. Impact</H2>
This vulnerability allows anyone with access to a user account
to gain root access.
<H2>III. Solution</H2>
The solutions to this vulnerability are to either (a) protect the file,
or (b) patch all the programs that trust it.
<P>Note that SunOS 4.1.3_U1 (Solaris 1.1.1) is _not_ vulnerable to this
problem.
<H3>A. To protect the file, make /etc/utmp writable only by root:</H3>
<PRE>
# chown root /etc/utmp<BR>
# chmod 644 /etc/utmp
</PRE>
<H3>B. Patches from Sun Microsystems</H3>
<PRE>
Program Patch ID Patch File Name
------- --------- ---------------
in.comsat 100272-07 100272-07.tar.Z
dump 100593-03 100593-03.tar.Z
syslogd 100909-02 100909-02.tar.Z
in.talkd 101480-01 101480-01.tar.Z
shutdown 101481-01 101481-01.tar.Z
write 101482-01 101482-01.tar.Z
Program BSD SVR4 MD5 Digital Signature
Checksum Checksum
------- --------- --------- --------------------------------
in.comsat 26553 39 64651 78 912ff4a0cc8d16a10eecbd7be102d45c
dump 52095 242 41650 484 cdba530226e8735fae2bd9bcbfa47dd0
syslogd 61539 108 38239 216 b5f70772384a3e58678c9c1f52d81190
in.talkd 47917 44 32598 88 5c3dfd6f90f739100cfa4aa4c97f01df
shutdown 46562 80 56079 159 bfc257ec795d05646ffa733d1c03855b
write 61148 41 48636 81 f93276529aa9fc25b35679ebf00b2d6f
</PRE>
<H3>C. Clarifications added April 1, 1994</H3>
<OL>
<LI>If you make /etc/utmp writable only by root, this should only affect
programs that allocate pseudo terminal interfaces and want to add
an appropriate entry to the /etc/utmp file. Such programs include
<I>script(1)</I>, <I>cmdtool(1)</I>, <I>gfxtool(1)</I>, <I>shelltool(1)</I>, and <I>tektool(1)</I>.
These programs will no longer be able to add an entry to /etc/utmp
which means that programs such as <I>who(1)</I>, <I>syslogd(1)</I>, and others
that use /etc/utmp will not know that an account is using that
pseudo tty.
<LI><P>No program should be made setuid root just to workaround this
problem. Setuid programs must be written very carefully to avoid
creating yet more vulnerabilities.
<LI><P>The installation instructions on the syslogd patch do not point out
that, until you stop and restart syslogd (or reboot the system),
the old version is still running and the security hole has not been
closed.
</LI></OL>
<!--#include virtual="/include/footer_nocopyright.html" -->
<P>Copyright 1994 Carnegie Mellon University.</P>
<HR>
Revision History
<PRE>
Sep. 19,1997 Updated copyright statement
Aug. 30, 1996 Information previously in the README was inserted
into the advisory.
Apr. 01, 1994 Intro. and Sec. III - added note that SunOS 4.1.3_U1 is not
vulnerable.
Apr. 01, 1994 Sec. III.C - added this new section, which contains
clarifications.
</PRE>
|