AUSCERT External Security Bulletin Redistribution
             ESB-98.100 -- SGI Security Advisory 19980602-01-PX
                        IRIX mediad(1M) Vulnerability
                                18 June 1998


Silicon Graphics Inc. has released the following advisory concerning
a vulnerability discovered in the default behaviour of the mediad(1M)
program that can lead to a root compromise of the system.  

Physical access to the removable media devices on the system and
a local account is required in order to exploit the mediad(1M)
vulnerability locally and remotely.

The following security bulletin is provided as a service to AusCERT's
members.  As AusCERT did not write this document, AusCERT has had no
control over its content.  As such, the decision to use any or all of this
information is the responsibility of each user or organisation, and should
be done so in accordance with site policies and procedures.

NOTE: This is only the original release of the security bulletin.  It will
not be updated when the original bulletin is.  If downloading at a later
date, it is recommended that the bulletin is retrieved from the original
authors to ensure that the information is still current.

Contact information for SGI is included in the Security Bulletin below.
If you have any questions or need further information, please contact them

Previous advisories and external security bulletins can be retrieved from:


If you believe that your system has been compromised, contact AusCERT or
your representative in FIRST (Forum of Incident Response and Security

Internet Email: auscert@auscert.org.au
Facsimile:	(07) 3365 7031
Telephone:	(07) 3365 4417 (International: +61 7 3365 4417)
		AusCERT personnel answer during Queensland business hours
		which are GMT+10:00 (AEST).
		On call after hours for emergencies.

- ------------------------BEGIN INCLUDED TEXT-----------------------


                Silicon Graphics Inc. Security Advisory

        Title:   IRIX mediad(1M) Vulnerability
        Number:  19980602-01-PX
        Date:    June 17, 1998

Silicon Graphics provides this information freely to the SGI user community
for its consideration, interpretation, implementation and use.   Silicon
Graphics recommends that this information be acted upon as soon as possible.

Silicon Graphics provides the information in this Security Advisory on
an "AS-IS" basis only, and disclaims all warranties with respect thereto,
express, implied or otherwise, including, without limitation, any warranty
of merchantability or fitness for a particular purpose.  In no event shall
Silicon Graphics be liable for any loss of profits, loss of business, loss
of data or for any indirect, special, exemplary, incidental or consequential
damages of any kind arising from your use of, failure to use or improper
use of any of the instructions or information in this Security Advisory.

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

The IRIX mediad(1M) daemon is used to monitor removable media devices on
Silicon Graphics Inc. (SGI) platforms.

Unfortunately, a vulnerability has been discovered in the default behavior
of the mediad(1M) program that can lead to a root compromise of the system.

Silicon Graphics Inc. 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.  This
issue will be corrected in future releases of IRIX.

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

The mediad(1M) daemon is installed by default on all IRIX 5.1 through
IRIX 6.4 systems.

Physical access to the removable media devices on the system and a local
account is required in order to exploit the mediad(1M) vulnerability
locally and remotely.

It is believed that this vulnerability has not been publically discussed.

- - ---------------------------
- - ---- Temporary Solution ---
- - ---------------------------

Although patches are available for this issue, it is realized that
there may be situations where installing the patches immediately may
not be possible.

The steps below can be used to remove the vulnerability by deactivating the
mediad(1M) program.

     1) Become the root user on the system.

                % /bin/su -

     2) Stop the currently running mediad(1M) daemon.

                # /etc/init.d/mediad stop

                           *** NOTE ***

                 With this workaround in place, removable media devices
                 will need to be mounted manually (see man mount(1M)).

     3) Turn off mediad(1M) during system start up.

                # chkconfig mediad off

                           *** NOTE ***

                After installing the patch, the mediad(1M) daemon needs to be
                reactivated during system startup with "chkconfig mediad on".

     4) Return to the previous user level.

                # exit

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

   OS Version     Vulnerable?     Patch #      Other Actions
   ----------     -----------     -------      -------------

   IRIX 3.x          no
   IRIX 4.x          no
   IRIX 5.0.x        no
   IRIX 5.1.x        yes          not avail    Note 1 & 2
   IRIX 5.2          yes          not avail    Note 1 & 2
   IRIX 5.3          yes         3191 & 3189   Note 3
   IRIX 6.0.x        yes          not avail    Note 1 & 2
   IRIX 6.1          yes          not avail    Note 1 & 2
   IRIX 6.2          yes         3192 & 3190   Note 3
   IRIX 6.3          yes            3109
   IRIX 6.4          yes            2891
   IRIX 6.5          no


     1) Upgrade to currently supported IRIX operating system.
     2) See "Temporary Solution" section.
     3) Both patches must be installed to fix this vulnerability.

Patches are available via anonymous FTP and your service/support provider.

The SGI anonymous FTP site is sgigate.sgi.com ( or its
mirror, ftp.sgi.com.  Security information and patches can be found
in the ~ftp/security and ~ftp/patches directories, respectfully.

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

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

Filename:                 README.patch.2891
Algorithm #1 (sum -r):    65078 14 README.patch.2891
Algorithm #2 (sum):       8485 14 README.patch.2891
MD5 checksum:             6CC3D4F3BE85D06B617F2B3BC5E1238A

Filename:                 patchSG0002891
Algorithm #1 (sum -r):    57624 7 patchSG0002891
Algorithm #2 (sum):       20791 7 patchSG0002891
MD5 checksum:             6223FA28BD1DBA56D5B23460C333B46E

Filename:                 patchSG0002891.eoe_man
Algorithm #1 (sum -r):    27548 213 patchSG0002891.eoe_man
Algorithm #2 (sum):       56163 213 patchSG0002891.eoe_man
MD5 checksum:             65AC7DF8E13EB22CCCF0396B14DF6DDC

Filename:                 patchSG0002891.eoe_sw
Algorithm #1 (sum -r):    45137 1334 patchSG0002891.eoe_sw
Algorithm #2 (sum):       48791 1334 patchSG0002891.eoe_sw
MD5 checksum:             5B41401985E06CCA4D9CA6047FAA24E6

Filename:                 patchSG0002891.idb
Algorithm #1 (sum -r):    25936 14 patchSG0002891.idb
Algorithm #2 (sum):       42399 14 patchSG0002891.idb
MD5 checksum:             F132FA43FE61F4029366B98EF046327F

Filename:                 README.patch.3109
Algorithm #1 (sum -r):    24400 15 README.patch.3109
Algorithm #2 (sum):       63902 15 README.patch.3109
MD5 checksum:             9C48F6AE738A3F4292FD0D6F000715AA

Filename:                 patchSG0003109
Algorithm #1 (sum -r):    46958 9 patchSG0003109
Algorithm #2 (sum):       39809 9 patchSG0003109
MD5 checksum:             F65CE9E7A3A5B6D2076296083581A22B

Filename:                 patchSG0003109.dev_sw
Algorithm #1 (sum -r):    46222 178 patchSG0003109.dev_sw
Algorithm #2 (sum):       23608 178 patchSG0003109.dev_sw
MD5 checksum:             C5D0EEE1B926775061D010539492FF5A

Filename:                 patchSG0003109.eoe_man
Algorithm #1 (sum -r):    64305 193 patchSG0003109.eoe_man
Algorithm #2 (sum):       53808 193 patchSG0003109.eoe_man
MD5 checksum:             82D8BB5FCF5A92DD05F10A0D396C8624

Filename:                 patchSG0003109.eoe_sw
Algorithm #1 (sum -r):    52088 2937 patchSG0003109.eoe_sw
Algorithm #2 (sum):       51862 2937 patchSG0003109.eoe_sw
MD5 checksum:             A792DD15489134388DF31F0F034D776B

Filename:                 patchSG0003109.idb
Algorithm #1 (sum -r):    48217 18 patchSG0003109.idb
Algorithm #2 (sum):       20609 18 patchSG0003109.idb
MD5 checksum:             EFA2C899D4C7F96DF14943565A635097

Filename:                 README.patch.3189
Algorithm #1 (sum -r):    18440 8 README.patch.3189
Algorithm #2 (sum):       40866 8 README.patch.3189
MD5 checksum:             B2DB0593855AE0616424A9ACEFB9472C

Filename:                 patchSG0003189
Algorithm #1 (sum -r):    23323 1 patchSG0003189
Algorithm #2 (sum):       29291 1 patchSG0003189
MD5 checksum:             67B68302F224057E26F8C529E4BCE85F

Filename:                 patchSG0003189.eoe2_sw
Algorithm #1 (sum -r):    16009 89 patchSG0003189.eoe2_sw
Algorithm #2 (sum):       2007 89 patchSG0003189.eoe2_sw
MD5 checksum:             CDAE8AC5BFE7153C0C86B35850FE6988

Filename:                 patchSG0003189.idb
Algorithm #1 (sum -r):    10773 1 patchSG0003189.idb
Algorithm #2 (sum):       36164 1 patchSG0003189.idb
MD5 checksum:             58EFBA4F9DF09BE37AF0438C5BE49401

Filename:                 README.patch.3190
Algorithm #1 (sum -r):    46303 8 README.patch.3190
Algorithm #2 (sum):       33172 8 README.patch.3190
MD5 checksum:             50A5ADF39FA1F9E1AD25550BFCC2D54F

Filename:                 patchSG0003190
Algorithm #1 (sum -r):    01530 1 patchSG0003190
Algorithm #2 (sum):       36083 1 patchSG0003190
MD5 checksum:             8F34CF99C67D0D227D327E4DE44D40FF

Filename:                 patchSG0003190.eoe_sw
Algorithm #1 (sum -r):    14428 92 patchSG0003190.eoe_sw
Algorithm #2 (sum):       26222 92 patchSG0003190.eoe_sw
MD5 checksum:             1ACA704D3473FB27E1F41E52C8A66425

Filename:                 patchSG0003190.idb
Algorithm #1 (sum -r):    05639 1 patchSG0003190.idb
Algorithm #2 (sum):       36623 1 patchSG0003190.idb
MD5 checksum:             F9CD42450BC0278E7A4E2A5D5E1C2015

Filename:                 README.patch.3191
Algorithm #1 (sum -r):    06248 11 README.patch.3191
Algorithm #2 (sum):       31452 11 README.patch.3191
MD5 checksum:             50E04AA8709A56B3D882B26B990E58BB

Filename:                 patchSG0003191
Algorithm #1 (sum -r):    04873 7 patchSG0003191
Algorithm #2 (sum):       45621 7 patchSG0003191
MD5 checksum:             B1DD09FD9CA77204DD0816A9D733FEDD

Filename:                 patchSG0003191.cadmin_sw
Algorithm #1 (sum -r):    24160 706 patchSG0003191.cadmin_sw
Algorithm #2 (sum):       25993 706 patchSG0003191.cadmin_sw
MD5 checksum:             75EFC916866460DB0CE205B781BD3DFF

Filename:                 patchSG0003191.eoe1_man
Algorithm #1 (sum -r):    24451 12 patchSG0003191.eoe1_man
Algorithm #2 (sum):       4655 12 patchSG0003191.eoe1_man
MD5 checksum:             7B690D29231DD4401845369CF88B080E

Filename:                 patchSG0003191.eoe1_sw
Algorithm #1 (sum -r):    07943 6 patchSG0003191.eoe1_sw
Algorithm #2 (sum):       58262 6 patchSG0003191.eoe1_sw
MD5 checksum:             D13FA81DF060BE27DA6F0478CA4D0476

Filename:                 patchSG0003191.eoe2_sw
Algorithm #1 (sum -r):    23461 135 patchSG0003191.eoe2_sw
Algorithm #2 (sum):       9315 135 patchSG0003191.eoe2_sw
MD5 checksum:             4BF6904EDCBB08A6C52664DABAE80817

Filename:                 patchSG0003191.idb
Algorithm #1 (sum -r):    21800 3 patchSG0003191.idb
Algorithm #2 (sum):       48342 3 patchSG0003191.idb
MD5 checksum:             889A725DA53EADA27B4C2E65F22A3296

Filename:                 README.patch.3192
Algorithm #1 (sum -r):    14737 9 README.patch.3192
Algorithm #2 (sum):       25649 9 README.patch.3192
MD5 checksum:             6CEF0C3571C086FBEC1E4FE8EF761DD2

Filename:                 patchSG0003192
Algorithm #1 (sum -r):    47927 3 patchSG0003192
Algorithm #2 (sum):       18593 3 patchSG0003192
MD5 checksum:             9251DC46B0F1EC1E783C40BB7EEF9D12

Filename:                 patchSG0003192.eoe_man
Algorithm #1 (sum -r):    60164 13 patchSG0003192.eoe_man
Algorithm #2 (sum):       53577 13 patchSG0003192.eoe_man
MD5 checksum:             7999BF4A4E20EA3EAB1AF82DBC233293

Filename:                 patchSG0003192.eoe_sw
Algorithm #1 (sum -r):    10318 160 patchSG0003192.eoe_sw
Algorithm #2 (sum):       30308 160 patchSG0003192.eoe_sw
MD5 checksum:             E2382D48673F2C3D15BAB821F5D570F7

Filename:                 patchSG0003192.idb
Algorithm #1 (sum -r):    30067 2 patchSG0003192.idb
Algorithm #2 (sum):       61532 2 patchSG0003192.idb
MD5 checksum:             360AA4EF675AA8EFEBB1B5CDE3534017

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

Silicon Graphics wishes to thank the Internet community at large for their
assistance in this matter.

- - ------------------------------------------------------------
- - ---- Silicon Graphics Inc. Security Information/Contacts ---
- - ------------------------------------------------------------

If there are questions about this document, email can be sent to


Silicon Graphics 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 information and patches
is sgigate.sgi.com (  Security information and patches
are located under the directories ~ftp/security and ~ftp/patches,
respectively. The Silicon Graphics Security Headquarters Web page is
accessible at the URL http://www.sgi.com/Support/security/security.html.

For issues with the patches on the FTP sites, email can be sent to

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


Silicon Graphics 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-request@sgi.com
subscribe wiretap <YourEmailAddress>

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.


Silicon Graphics provides a comprehensive customer World Wide Web site.
This site is located at http://www.sgi.com/Support/security/security.html.


For reporting *NEW* SGI security issues, email can be sent to
security-alert@sgi.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, Silicon
  Graphics is appropriately credited and the document retains and
  includes its valid PGP signature.

Version: 2.6.2


- -------------------------END INCLUDED TEXT------------------------

Version: 2.6.3i
Charset: noconv
Comment: ftp://ftp.auscert.org.au/pub/auscert/AUSCERT_PGP.key