[VulnWatch] IRIX 6.5.21 NFS export vulnerability

From: SGI Security Coordinator (agent99_at_sgi.com)
Date: 09/16/03

  • Next message: Michal Zalewski: "[VulnWatch] Windows URG mystery solved!"
    Date: Tue, 16 Sep 2003 13:55:18 -0700
    To: agent99@sgi.com


                               SGI Security Advisory

      Title: IRIX 6.5.21 NFS export vulnerability
      Number: 20030901-01-P
      Date: September 16, 2003
      Reference: CVE CAN-2003-0680
      Reference: SGI BUG 899846
      Fixed in: Patches 5317 and 5318 for IRIX 6.5.21

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

    SGI 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
    SGI 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 ---
    - -----------------------

    It has been reported that under certain conditions a NFS client can
    avoid read-only restrictions on filesystems exported via NFS from a
    server running IRIX 6.5.21 and mount them in read/write mode.

    The Common Vulnerabilities and Exposures project (cve.mitre.org) has
    assigned the name CAN-2003-0680 to this vulnerability:

    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. This issue has been
    corrected in future releases of IRIX.

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

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

      # /bin/uname -R

    That will return a result similar to the following:

      # 6.5 6.5.21f

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

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

    There is no effective workaround available for this vulnerability.
    SGI recommends either upgrading to IRIX 6.5.22 (when available),
    or installing the appropriate patch for IRIX 6.5.21 from the listing below.

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

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

    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 no Notes 1
    IRIX 6.5.1 no Notes 1
    IRIX 6.5.2 no Notes 1
    IRIX 6.5.3 no Notes 1
    IRIX 6.5.4 no Notes 1
    IRIX 6.5.5 no Notes 1
    IRIX 6.5.6 no Notes 1
    IRIX 6.5.7 no Notes 1
    IRIX 6.5.8 no Notes 1
    IRIX 6.5.9 no Notes 1
    IRIX 6.5.10 no Notes 1
    IRIX 6.5.11 no Notes 1
    IRIX 6.5.12 no Notes 1
    IRIX 6.5.13 no Notes 1
    IRIX 6.5.14 no Notes 1
    IRIX 6.5.15 no Notes 1
    IRIX 6.5.16 no Notes 1
    IRIX 6.5.17 no Notes 1
    IRIX 6.5.18m no Notes 2
    IRIX 6.5.18f no Notes 2
    IRIX 6.5.19m no Notes 2
    IRIX 6.5.19f no Notes 2
    IRIX 6.5.20m no Notes 2
    IRIX 6.5.20f no Notes 2
    IRIX 6.5.21m yes 5317 Notes 2 & 3
    IRIX 6.5.21f yes 5318 Notes 2 & 3
    IRIX 6.5.22 no


         1) This version of the IRIX operating has been retired.
            Upgrade to an actively supported IRIX operating system.
            See http://support.sgi.com 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

         3) Install the required patch(es) based on your operating release.

                  ##### Patch File Checksums ####
    Filename: README.patch.5317
    Algorithm #1 (sum -r): 58922 9 README.patch.5317
    Algorithm #2 (sum): 7391 9 README.patch.5317
    MD5 checksum: 50A9B7DC82EFF1FAF96AC77DB44C5F58

    Filename: patchSG0005317
    Algorithm #1 (sum -r): 43256 2 patchSG0005317
    Algorithm #2 (sum): 62576 2 patchSG0005317
    MD5 checksum: 1C50658B51328CF571CB2EBF30A1252D

    Filename: patchSG0005317.eoe_sw
    Algorithm #1 (sum -r): 55756 2261 patchSG0005317.eoe_sw
    Algorithm #2 (sum): 24968 2261 patchSG0005317.eoe_sw
    MD5 checksum: FF2AE9E7C86A717190B4DDE40EEBC8DD

    Filename: patchSG0005317.idb
    Algorithm #1 (sum -r): 61112 26 patchSG0005317.idb
    Algorithm #2 (sum): 8958 26 patchSG0005317.idb
    MD5 checksum: 6775EFB2B97576F07803FAE9D77C75B9

    Filename: patchSG0005317.nfs_sw
    Algorithm #1 (sum -r): 29306 5331 patchSG0005317.nfs_sw
    Algorithm #2 (sum): 62999 5331 patchSG0005317.nfs_sw
    MD5 checksum: 6415ADF1E4ADFB0D412AD7083D6CB2B8

    Filename: README.patch.5318
    Algorithm #1 (sum -r): 11334 9 README.patch.5318
    Algorithm #2 (sum): 7077 9 README.patch.5318
    MD5 checksum: 0180730DDEC857D08021602A6C4F19B9

    Filename: patchSG0005318
    Algorithm #1 (sum -r): 17201 2 patchSG0005318
    Algorithm #2 (sum): 65068 2 patchSG0005318
    MD5 checksum: E5230214F4D45719E089E66242377053

    Filename: patchSG0005318.eoe_sw
    Algorithm #1 (sum -r): 61230 2281 patchSG0005318.eoe_sw
    Algorithm #2 (sum): 9254 2281 patchSG0005318.eoe_sw
    MD5 checksum: 7444298E987C8556DFEBF81FA199DD85

    Filename: patchSG0005318.idb
    Algorithm #1 (sum -r): 11527 26 patchSG0005318.idb
    Algorithm #2 (sum): 8870 26 patchSG0005318.idb
    MD5 checksum: D5CD8B34434E78BE55D3411FDB053F09

    Filename: patchSG0005318.nfs_sw
    Algorithm #1 (sum -r): 30425 5435 patchSG0005318.nfs_sw
    Algorithm #2 (sum): 9952 5435 patchSG0005318.nfs_sw
    MD5 checksum: FE7D3F51EF9183A605FBD463760E8A3E

    - -------------
    - --- Links ---
    - -------------

    Patches are available via the web, anonymous FTP and from your SGI
    service/support provider.

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

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

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

    SGI freeware updates for IRIX can be found at:

    SGI fixes for SGI open sourced code can be found on:

    SGI patches and RPMs for Linux can be found at:

    SGI patches for Windows NT or 2000 can be found at:

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

    IRIX 6.5 Maintenance Release Streams can be found at:

    IRIX 6.5 Software Update CDs can be obtained from:

    The primary SGI anonymous FTP site for security advisories and patches
    is patches.sgi.com ( 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.

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

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


    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 ( 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:

    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.


    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
    or by sending email to SGI as outlined below.

    % mail wiretap-request@sgi.com
    subscribe wiretap <YourEmailAddress such as aaanalyst@sgi.com >

    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.


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


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

    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, SGI is appropriately credited and the document retains and
          includes its valid PGP signature.

    Version: 2.6.2

    -----END PGP SIGNATURE-----

  • Next message: Michal Zalewski: "[VulnWatch] Windows URG mystery solved!"

    Relevant Pages