System Security Enhancement (SSE) 011 - 16th March 1998 Problem: A potential vulnerability has been discovered by inspection of the source code of ftpd, the ftp server. This is the same vulnerability as reported in CERT advisory CA-97.16. We have not heard of any incidents where this vulnerability has been exploited, although it could be used to give an attacker root access in certain circumstances. The enclosed patch should be applied as soon as possible. Patch: A replacement ftp daemon is supplied for each of the following SCO operating systems: - SCO Open Desktop/Open Server Release 3.0 - SCO CMW+ 3.0 - SCO UnixWare 2.1 For OpenServer 5.0.0 and OpenServer 5.0.2, SLS OSS449F includes a fixed version of ftpd. OSS449F should be installed rather than SSE011. For OpenServer 5.0.4, Release Supplement RS504C includes a fixed version of ftpd. RS504C should be installed rather than SSE011. Note that UnixWare 7 is not vulnerable to this attack. Installation: Perform the following steps logged in as root: 1. Create a temporary directory, and copy SSE011 into it: # mkdir /tmp/sse011 # cp sse011.tar.Z /tmp/sse011 2. uncompress the tar file: # cd /tmp/sse011 # uncompress sse011.tar.Z 3. extract the files from the tar file: # tar xvf sse011.tar 4. Replace your existing ftp daemon with the updated daemon: - For SCO Open Desktop/Open Server 3.0: # cd /etc # mv ftpd ftpd.old (saves existing daemon) # mv /tmp/sse011/ftpd.odt3 ftpd # cd / # fixperm etc/perms/tcprt (sets file permissions) - For SCO CMW+ 3.0: # cd /etc # mv ftpd ftpd.old (saves existing daemon) # mv /tmp/sse011/ftpd.cmw3 ftpd # setfiles (sets file permissions) - For SCO UnixWare 2.1: # cd /usr/sbin # mv in.ftpd in.ftpd.old (saves existing daemon) # mv /tmp/sse011/in.ftpd . # chmod 555 in.ftpd # chown bin:bin in.ftpd (sets file permissions) It is not necessary to reboot your system - the new ftp daemon will now be used for all new incoming ftp sessions. Disclaimer: SCO believes that this patch addresses the reported vulnerability. However, in order that it be released as soon as possible, this patch has not been fully tested or packaged to SCO's normal exacting standards. For that reason, this patch is not officially supported. Official supported and packaged fixes for current SCO products will be available in due course.