Original issue date: January 13, 1993<BR>
Last revised: September 19, 1997<BR>
Attached copyright statement

<P>A complete revision history is at the end of this file.

<B>
THIS IS A REVISED CERT ADVISORY.<BR>
IT CONTAINS NEW INFORMATION REGARDING AVAILABILITY OF IMAGE KITS<BR>
SUPERSEDES CERT ADVISORY CA-92.17<BR>
</B>

<P>The CERT Coordination Center has received information concerning a
vulnerability in the NIS ypbind module for the Hewlett-Packard (HP)
HP/UX Operating System for series 300, 700, and 800 computers. 

<P>HP has provided revised patches for all of the HP/UX level 8 releases
(8.0, 8.02, 8.06, and 8.07).  This problem is fixed in HP/UX 9.0.
The following patches have been superseded:

<P><CENTER>
<TABLE WIDTH=60%>
<TR><TH WIDTH=40%>Patch ID</TH><TH>Replaced by Patch ID</TH></TR>
<TR><TD>PHNE_1359</TD><TD>PHNE_1706</TD></TR>
<TR><TD>PHNE_1360</TD><TD>PHNE_1707</TD></TR>
<TR><TD>PHNE_1361</TD><TD>PHNE_1708</TD></TR>
</TABLE></CENTER>

<P>All HP NIS clients and servers running ypbind should obtain and 
install the patch appropriate for their machine's architecture
as described below.

<P><HR>

<P>
<H2>I. Description</H2>

<P>A vulnerability in HP NIS allows unauthorized access to NIS data.

<P>
<H2>II. Impact</H2>

<P>Root on a remote host running any vendor's implementation of NIS
can gain root access on any local host running HP's NIS ypbind. 
Local users of a host running HP's NIS ypbind can also gain root access.

<P>
<H2>III. Solution</H2>

<P>
<OL>
<LI>All HP NIS clients and servers running ypbind should obtain and 
install the patch appropriate for their machine's architecture.

<P>These patches contain a version of ypbind that only accepts ypset
requests from a superuser port on the local host.  This prevents
a non-superuser program from sending rogue ypset requests to ypbind.
They also include the mod from the superseded patches which prevented
a superuser on a remote system from issuing a ypset -h command
to the local system and binding the system to a rogue ypserver.

<P>These patches may be obtained from HP via FTP (this is NOT
anonymous FTP) or the HP SupportLine.  To obtain HP security
patches, you must first register with the HP SupportLine.
The registration instructions are available via
anonymous FTP at cert.org (192.88.209.5) in the file
&quot;pub/vendors/hp/supportline_and_patch_retrieval&quot;.

<P>The new patch files are:

<P>
<PRE>
Architecture Patch ID   Filename                               Checksum
------------ --------   --------                               --------
Series 300   PHNE_1706  /hp-ux_patches/s300_400/8.X/PHNE_1706  38955 212
Series 700   PHNE_1707  /hp-ux_patches/s700/8.X/PHNE_1707        815 311
Series 800   PHNE_1708  /hp-ux_patches/s800/8.X/PHNE_1708      56971 299
</PRE>

<LI><P>The instructions for installing the patch are provided in the
PHNE_xxxx.text file (this file is created after the patch has
been unpacked).

<P>The checksums listed above are for the patch archive files from HP.
Once unpacked, each shell archive contains additional checksum 
information in the file &quot;patchfilename.text&quot;.  This checksum is
applicable to the binary patch file &quot;patchfilename.updt&quot;.

<P></OL>
If you have any questions about obtaining or installing the patches,
contact the USA HP SupportLine at 415-691-3888, or your local HP
SupportLine number.  Please note that the telephone numbers in this
advisory are appropriate for the USA and Canada. 

<P><HR>
The CERT Coordination Center wishes to thank Brian Kelley of Ford Motor
Company for bringing this vulnerability to our attention.  We would also
like to thank Hewlett-Packard for their response to this problem. 

<!--#include virtual="/include/footer_nocopyright.html" -->
<P>Copyright 1993 Carnegie Mellon University.</P>

<HR>

Revision History
<PRE>
September 19,1997  Attached Copyright Statement
</PRE>