-----BEGIN PGP SIGNED MESSAGE-----

______________________________________________________________________________

                          SGI Security Advisory

         Title: rpcbind/fsr_efs/mv/errhook/uux vulnerabilities
        Number: 20020903-01-P
          Date: October 3, 2002

______________________________________________________________________________

- -----------------------
- --- Issue Specifics ---
- -----------------------

It's been reported that there are several vulnerabilities in user-level
commands supplied with IRIX 6.5:

  o rpcbind, when using the "-w" switch, follows symlinks and should not

  o Some temporary files used by the desktop are world-writable

  o uux, which has sgid permissions, has a buffer overrun vulnerability

  o fsr_efs follows symlinks and should not

  o the mv command creates the directory with world-writable permissions
     when it is used to move a directory.

SGI has investigated the issue and recommends the following steps for
neutralizing the exposure. It is HIGHLY RECOMMENDED that these measures be
implemented on ALL vulnerable SGI systems.

These issues have been corrected in future releases of IRIX.

- --------------
- --- Impact ---
- --------------

The rpcbind binary is part of the optional "eoe.sw.svr4net" package and is
not installed by default.

The fsr_efs and mv binaries are installed by default on IRIX 6.5
systems as part of "eoe.sw.base".

The IRIX Indigo Magic Desktop is installed by default as part of
"desktop_eoe.sw".
The uux binary is part of the optional "eoe.sw.uucp" package and is not
installed by default.

To determine the version of IRIX you are running, execute the following
command:

  # uname -R

That will return a result similar to the following:

  # 6.5 6.5.16f

The first number ("6.5") is the release name, the second ("6.5.16f" in this
case) is the extended release name. The extended release name is the
"version" we refer to throughout this document.

To see if the affected programs are installed, execute the following
commands:

  # versions eoe.sw.svr4net
  I = Installed, R = Removed

   Name Date Description

   I eoe 07/19/2002 IRIX Execution Environment, 6.5.17f
   I eoe.sw 07/19/2002 IRIX Execution Environment Software
   I eoe.sw.svr4net 07/19/2002 System V Release 4 Networking

  # versions desktop_eoe.sw
  I = Installed, R = Removed

   Name Date Description

   I desktop_eoe 07/15/2002 IRIX Interactive Desktop, 6.5.16f
   I desktop_eoe.sw 07/15/2002 IRIX Interactive Desktop Software,
6.5.16f
   I desktop_eoe.sw.Confidence 07/15/2002 Desktop Confidence Tests
   I desktop_eoe.sw.Desks 07/15/2002 Desktop Desks
   I desktop_eoe.sw.control_panels 07/15/2002 Desktop Customization Panels
   I desktop_eoe.sw.envm 07/15/2002 Desktop Environment
   I desktop_eoe.sw.share 07/15/2002 Desktop Shared Files
   I desktop_eoe.sw.toolchest 07/15/2002 Desktop Toolchest

  # versions eoe.sw.uucp
  I = Installed, R = Removed

   Name Date Description

   I eoe 07/15/2002 IRIX Execution Environment, 6.5.16f
   I eoe.sw 07/15/2002 IRIX Execution Environment Software
   I eoe.sw.uucp 07/15/2002 UUCP Utilities

It is not necessary to check for eoe.sw.base. If it is not installed, you
wouldn't have the "versions" command to check it with. It's installed.
Trust us on this.

If the output of the commands shows results similar to the above, then the
programs are installed and the system may be vulnerable.

- ----------------------------
- --- Temporary Workaround ---
- ----------------------------

SGI understands that there are times when upgrading the operating system or
installing patches are inconvenient or not possible. In those instances, we
recommend the following workarounds:

  o rpcbind... don't use the "-w" option. Make sure that switch is not
     used in /etc/config/rpcbind.options.

  o Desktop temporary files... there is no effective workaround for this
     issue, other than making each user's home directory readable only by
     the user.

  o uux... there is no effective workaround for this issue. However, if
     the only reason you have eoe.sw.uucp installed is for PPP support,
     you can safely chmod -x uux.

  o fsr_efs... there is no effective workaround for this issue, but if you
     don't have a EFS fs mounted rw, you can safely chmod -x fsr_efs.

  o mv command... there is no effective workaround for this issue.

- ----------------
- --- Solution ---
- ----------------

SGI has provided a series of patches for these vulnerabilities. Our
recommendation is to upgrade to IRIX 6.5.18 when available, or install the
appropriate patch.

   OS Version Vulnerable? Patch # Other Actions
   ---------- ----------- ------- -------------
   IRIX 3.x unknown Note 1
   IRIX 4.x unknown Note 1
   IRIX 5.x unknown Note 1
   IRIX 6.0.x unknown Note 1
   IRIX 6.1 unknown Note 1
   IRIX 6.2 unknown Note 1
   IRIX 6.3 unknown Note 1
   IRIX 6.4 unknown Note 1
   IRIX 6.5 yes Notes 2 & 4
   IRIX 6.5.1 yes Notes 2 & 4
   IRIX 6.5.2 yes Notes 2 & 4
   IRIX 6.5.3 yes Notes 2 & 4
   IRIX 6.5.4 yes Notes 2 & 4
   IRIX 6.5.5 yes Notes 2 & 4
   IRIX 6.5.6 yes Notes 2 & 4
   IRIX 6.5.7 yes Notes 2 & 4
   IRIX 6.5.8 yes Notes 2 & 4
   IRIX 6.5.9 yes Notes 2 & 4
   IRIX 6.5.10 yes Notes 2 & 4
   IRIX 6.5.11 yes Notes 2 & 4
   IRIX 6.5.12 yes Notes 2 & 4
   IRIX 6.5.13m yes 4771 Notes 2 & 3
   IRIX 6.5.13 yes 4772 Notes 2 & 3
   IRIX 6.5.14m yes 4771 Notes 2 & 3
   IRIX 6.5.14 yes 4772 Notes 2 & 3
   IRIX 6.5.15m yes 4771 Notes 2 & 3
   IRIX 6.5.15 yes 4772 Notes 2 & 3
   IRIX 6.5.16m yes 4771 Notes 2 & 3
   IRIX 6.5.16 yes 4772 Notes 2 & 3
   IRIX 6.5.17m yes 4771 Notes 2 & 3
   IRIX 6.5.17 yes 4772 Notes 2 & 3
   IRIX 6.5.18 no

   NOTES

     1) This version of the IRIX operating has been retired. Upgrade to an
        actively supported IRIX operating system. See
        http://support.sgi.com/irix/news/index.html#policy for more
        information.

     2) If you have not received an IRIX 6.5.X CD for IRIX 6.5, contact your
        SGI Support Provider or URL: http://support.sgi.com/irix/swupdates/

     3) Install the appropriate patch or upgrade to IRIX 6.5.18 when it
        becomes available.

     4) Upgrade to 6.5.18 when it becomes available

                ##### Patch File Checksums ####

The actual patch will be a tar file containing the following files:

Filename: README.patch.4771
Algorithm #1 (sum -r): 14179 9 README.patch.4771
Algorithm #2 (sum): 13590 9 README.patch.4771
MD5 checksum: 873E0220FD5EB243A2F611A378474B8B

Filename: patchSG0004771
Algorithm #1 (sum -r): 56421 8 patchSG0004771
Algorithm #2 (sum): 14268 8 patchSG0004771
MD5 checksum: 55519774C3D7DF4727310E557C73856C

Filename: patchSG0004771.eoe_man
Algorithm #1 (sum -r): 63025 8 patchSG0004771.eoe_man
Algorithm #2 (sum): 7979 8 patchSG0004771.eoe_man
MD5 checksum: 219D23BAA4BD0465D28A17C9924CEC95

Filename: patchSG0004771.eoe_sw
Algorithm #1 (sum -r): 48036 648 patchSG0004771.eoe_sw
Algorithm #2 (sum): 33128 648 patchSG0004771.eoe_sw
MD5 checksum: D47080717C1383E2846772A054C9916E

Filename: patchSG0004771.idb
Algorithm #1 (sum -r): 33220 3 patchSG0004771.idb
Algorithm #2 (sum): 28385 3 patchSG0004771.idb
MD5 checksum: 59E205D4CCBDDEF1086034F9D3532D8E

Filename: patchSG0004771.sysmon_sw
Algorithm #1 (sum -r): 53618 97 patchSG0004771.sysmon_sw
Algorithm #2 (sum): 10219 97 patchSG0004771.sysmon_sw
MD5 checksum: 456619AFC17FF7D2707D3AADF307E038

Filename: README.patch.4772
Algorithm #1 (sum -r): 28400 9 README.patch.4772
Algorithm #2 (sum): 13520 9 README.patch.4772
MD5 checksum: 48AF9D730F79B6E1CCE7D1A72771EE73

Filename: patchSG0004772
Algorithm #1 (sum -r): 49065 8 patchSG0004772
Algorithm #2 (sum): 20173 8 patchSG0004772
MD5 checksum: 5B396A2CCD2DC360A54E41E98AEF76FB

Filename: patchSG0004772.eoe_man
Algorithm #1 (sum -r): 63025 8 patchSG0004772.eoe_man
Algorithm #2 (sum): 7979 8 patchSG0004772.eoe_man
MD5 checksum: 219D23BAA4BD0465D28A17C9924CEC95

Filename: patchSG0004772.eoe_sw
Algorithm #1 (sum -r): 44167 658 patchSG0004772.eoe_sw
Algorithm #2 (sum): 48150 658 patchSG0004772.eoe_sw
MD5 checksum: 5F3C419BA48698904824D932723D10EE

Filename: patchSG0004772.idb
Algorithm #1 (sum -r): 10695 3 patchSG0004772.idb
Algorithm #2 (sum): 28362 3 patchSG0004772.idb
MD5 checksum: CA3743F3082B8D463BEFC052FE0A4D0C

Filename: patchSG0004772.sysmon_sw
Algorithm #1 (sum -r): 15278 97 patchSG0004772.sysmon_sw
Algorithm #2 (sum): 10004 97 patchSG0004772.sysmon_sw
MD5 checksum: 37744FDE6172A7C5659992C8D3ED4025

- ------------------
- --- References ---
- ------------------

SGI Security Advisories can be found at:
http://www.sgi.com/support/security/ and
ftp://patches.sgi.com/support/free/security/advisories/

SGI Security Patches can be found at:
http://www.sgi.com/support/security/ and
ftp://patches.sgi.com/support/free/security/patches/

SGI patches for IRIX can be found at the following patch servers:
http://support.sgi.com/irix/ and ftp://patches.sgi.com/

SGI freeware updates for IRIX can be found at:
http://freeware.sgi.com/

SGI fixes for SGI open sourced code can be found on:
http://oss.sgi.com/projects/

SGI patches and RPMs for Linux can be found at:
http://support.sgi.com/linux/ or
http://oss.sgi.com/projects/sgilinux-combined/download/security-fixes/

SGI patches for Windows NT or 2000 can be found at:
http://support.sgi.com/nt/

IRIX 5.2-6.4 Recommended/Required Patch Sets can be found at:
http://support.sgi.com/irix/ and ftp://patches.sgi.com/support/patchset/

IRIX 6.5 Maintenance Release Streams can be found at:
http://support.sgi.com/colls/patches/tools/relstream/index.html

IRIX 6.5 Software Update CDs can be obtained from:
http://support.sgi.com/irix/swupdates/

The primary SGI anonymous FTP site for security advisories and patches is
patches.sgi.com (216.32.174.211). Security advisories and patches are
located under the URL ftp://patches.sgi.com/support/free/security/

For security and patch management reasons, ftp.sgi.com (mirrors
patches.sgi.com security FTP repository) lags behind and does not do a
real-time update.

- ------------------------
- --- Acknowledgments ----
- ------------------------

SGI wishes to thank FIRST, Walter Roberson, NASA JPL, University of Alaska
and the users of the Internet Community at large for their assistance in
this matter.

- -----------------------------------------
- --- SGI Security Information/Contacts ---
- -----------------------------------------

If there are questions about this document, email can be sent to
security-infosgi.com.

                      ------oOo------

SGI provides security information and patches for use by the entire SGI
community. This information is freely available to any person needing the
information and is available via anonymous FTP and the Web.

The primary SGI anonymous FTP site for security advisories and patches is
patches.sgi.com (216.32.174.211). Security advisories and patches are
located under the URL ftp://patches.sgi.com/support/free/security/

The SGI Security Headquarters Web page is accessible at the URL:
http://www.sgi.com/support/security/

For issues with the patches on the FTP sites, email can be sent to
security-infosgi.com.

For assistance obtaining or working with security patches, please
contact your SGI support provider.

                      ------oOo------

SGI provides a free security mailing list service called wiretap and
encourages interested parties to self-subscribe to receive (via email) all
SGI Security Advisories when they are released. Subscribing to the mailing
list can be done via the Web
(http://www.sgi.com/support/security/wiretap.html) or by sending email to
SGI as outlined below.

% mail wiretap-requestsgi.com
subscribe wiretap <YourEmailAddress>
end
^d

In the example above, <YourEmailAddress> is the email address that you wish
the mailing list information sent to. The word end must be on a separate
line to indicate the end of the body of the message. The control-d (^d) is
used to indicate to the mail program that you are finished composing the
mail message.

                      ------oOo------

SGI provides a comprehensive customer World Wide Web site. This site is
located at http://www.sgi.com/support/security/ .

                      ------oOo------

If there are general security questions on SGI systems, email can be sent to
security-infosgi.com.

For reporting *NEW* SGI security issues, email can be sent to
security-alertsgi.com or contact your SGI support provider. A support
contract is not required for submitting a security report.

______________________________________________________________________________
      This information is provided freely to all interested parties
      and may be redistributed provided that it is not altered in any
      way, SGI is appropriately credited and the document retains and
      includes its valid PGP signature.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBPZyGCrQ4cFApAP75AQFg3wP/UkCwmEWoQhoHxncW74a4BY8lc5cJjwwS
AqPRcQJF3vlegnHlDD3D+RJxze1I1RxKUjo3eV0xKYzVJL6tBvozr54sCNmYJ9c2
9ismfGfLWDv7F5tUYJs4c0KhYH9GjVRpWgf8nep8RJsfq+x7ASAZKlKoF3ggDs16
5iEYzP9PAYA=
=3SAd
-----END PGP SIGNATURE-----

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]