TUCoPS :: SGI :: n-075.txt

SGI xfsdump Vulnerability (CIAC N-075)

  
             __________________________________________________________

                       The U.S. Department of Energy
                   Computer Incident Advisory Capability
                           ___  __ __    _     ___
                          /       |     /_\   /
                          \___  __|__  /   \  \___
             __________________________________________________________

                             INFORMATION BULLETIN

                           SGI xfsdump vulnerability
                     [SGI Security Advisory 20030404-01-P]

April 11, 2003 21:00 GMT                                          Number N-075
______________________________________________________________________________
PROBLEM:       SGI has received reports that xfsdump creates quota information
               files insecurely.
PLATFORM:      IRIX 6.5 through IRIX 6.5.19f systems
DAMAGE:        Vulnerability could possibly lead to a root exploit by a local
               user.
SOLUTION:      SGI recommends either upgrading to IRIX 6.5.20 (when
               available), or installing the appropriate patch.
______________________________________________________________________________
VULNERABILITY  The risk is MEDIUM. A local user could possibly gain root
ASSESSMENT:    privileges.  xfsdump is installed by default on IRIX 6.5 
               systems.
______________________________________________________________________________
LINKS:
 CIAC BULLETIN:      http://www.ciac.org/ciac/bulletins/n-075.shtml
______________________________________________________________________________

[***** Start SGI Security Advisory 20030404-01-P *****]

SGI Security Advisory

Title    : xfsdump creates files insecurely
Number   : 20030404-01-P
Date     : April 10, 2003
Reference: CVE CAN-2003-0173
Reference: SGI BUG 885222
Fixed in : IRIX 6.5.20 (when available) or patches 5059 and 5060
______________________________________________________________________________

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

It's been reported that xfsdump creates quota information files insecurely,
possibly leading to a root exploit by a local user.

See: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0173

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 with patches and in future releases of
IRIX.


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

The xfsdump binary is installed by default on IRIX 6.5 systems as part of
eoe.sw.base.

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

  # /bin/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.


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

There is no effective workaround available for these problems if you need to
use xfsdump on xfs filesystems with quotas.  SGI recommends either upgrading
to IRIX 6.5.20 (when available), or installing the appropriate patch from
the listing below.


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

SGI has provided a series of patches for these vulnerabilities. Our
recommendation is to upgrade to IRIX 6.5.20 (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 & 3
   IRIX 6.5.1        yes                       Notes 2 & 3
   IRIX 6.5.2        yes                       Notes 2 & 3
   IRIX 6.5.3        yes                       Notes 2 & 3
   IRIX 6.5.4        yes                       Notes 2 & 3
   IRIX 6.5.5        yes                       Notes 2 & 3
   IRIX 6.5.6        yes                       Notes 2 & 3
   IRIX 6.5.7        yes                       Notes 2 & 3
   IRIX 6.5.8        yes                       Notes 2 & 3
   IRIX 6.5.9        yes                       Notes 2 & 3
   IRIX 6.5.10       yes                       Notes 2 & 3
   IRIX 6.5.11       yes                       Notes 2 & 3
   IRIX 6.5.12       yes                       Notes 2 & 3
   IRIX 6.5.13       yes                       Notes 2 & 3
   IRIX 6.5.14       yes                       Notes 2 & 3
   IRIX 6.5.15       yes                       Notes 2 & 3
   IRIX 6.5.16m      yes           5059        Notes 2 & 4
   IRIX 6.5.16f      yes           5060        Notes 2 & 4
   IRIX 6.5.17m      yes           5059        Notes 2 & 4
   IRIX 6.5.17f      yes           5060        Notes 2 & 4
   IRIX 6.5.18m      yes           5059        Notes 2 & 4
   IRIX 6.5.18f      yes           5060        Notes 2 & 4
   IRIX 6.5.19m      yes           5059        Notes 2 & 4
   IRIX 6.5.19f      yes           5060        Notes 2 & 4
   IRIX 6.5.20        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/ 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) Upgrade to IRIX 6.5.20 (when available)

     4) Upgrade to IRIX 6.5.20 (when available) or install the patch

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

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

Filename:                 README.patch.5059
Algorithm #1 (sum -r):    42028 10 README.patch.5059
Algorithm #2 (sum):       2632 10 README.patch.5059
MD5 checksum:             1AC8B7BE35C147D14C6BE8E57BBE3506

Filename:                 patchSG0005059
Algorithm #1 (sum -r):    35357 4 patchSG0005059
Algorithm #2 (sum):       54133 4 patchSG0005059
MD5 checksum:             95B0D4C4F6EEA7BF3485B2770F979E0A

Filename:                 patchSG0005059.eoe_man
Algorithm #1 (sum -r):    40035 6 patchSG0005059.eoe_man
Algorithm #2 (sum):       1308 6 patchSG0005059.eoe_man
MD5 checksum:             9AF1B72719A03646FEC03FF8C172FB73

Filename:                 patchSG0005059.eoe_sw
Algorithm #1 (sum -r):    29249 359 patchSG0005059.eoe_sw
Algorithm #2 (sum):       22794 359 patchSG0005059.eoe_sw
MD5 checksum:             3B62950D43457B4F56D50257500FC443

Filename:                 patchSG0005059.idb
Algorithm #1 (sum -r):    59650 2 patchSG0005059.idb
Algorithm #2 (sum):       59732 2 patchSG0005059.idb
MD5 checksum:             FA2044B2B051A7AAA423CC9B816B3E22

Filename:                 README.patch.5060
Algorithm #1 (sum -r):    33966 10 README.patch.5060
Algorithm #2 (sum):       2418 10 README.patch.5060
MD5 checksum:             D543B3BE2BFFE152ECF88ECDFD7A8582

Filename:                 patchSG0005060
Algorithm #1 (sum -r):    14237 4 patchSG0005060
Algorithm #2 (sum):       59998 4 patchSG0005060
MD5 checksum:             92AFE1F0DDE38503FB48A02CBBE35D80

Filename:                 patchSG0005060.eoe_man
Algorithm #1 (sum -r):    07693 6 patchSG0005060.eoe_man
Algorithm #2 (sum):       41147 6 patchSG0005060.eoe_man
MD5 checksum:             47A55B469DEAEA18136C7540A01435D5

Filename:                 patchSG0005060.eoe_sw
Algorithm #1 (sum -r):    31162 361 patchSG0005060.eoe_sw
Algorithm #2 (sum):       15461 361 patchSG0005060.eoe_sw
MD5 checksum:             5ECD41272723A9B80D56AF17265FDDA4

Filename:                 patchSG0005060.idb
Algorithm #1 (sum -r):    28575 2 patchSG0005060.idb
Algorithm #2 (sum):       59664 2 patchSG0005060.idb
MD5 checksum:             D6F4923E4BF2677607A892CFA2101AF7

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

SGI wishes to thank Ethan Benson, Nathan Scott and Debian for their
assistance in this matter.


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

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

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:
http://support.sgi.com/

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

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
security-info@sgi.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.  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-info@sgi.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-request@sgi.com
subscribe wiretap <YourEmailAddress such as aaanalyst@sgi.com >
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-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.
	  
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBPpWf6LQ4cFApAP75AQGtTQQAhastm5/DlpwqIgeJRANYZUi54JERjBmj
MZU+mP768cvUz1/13De/qT6j7IbpoH5dlngcGIcMBWycCY6A0oOjEP3gx0jXhf/u
CR6FkfzmH7/Eg/QYMqyWaH3Aeugqmr1Qg0vZ9JT2pvQFsEiRqUJSmVcqcCpnEn0B
rRw+Yh4pLwg=
=ABnC
-----END PGP SIGNATURE-----

[***** End SGI Security Advisory 20030404-01-P *****]
_______________________________________________________________________________

CIAC wishes to acknowledge the contributions of SGI  for the
information contained in this bulletin.
_______________________________________________________________________________

CIAC, the Computer Incident Advisory Capability, is the computer
security incident response team for the U.S. Department of Energy
(DOE) and the emergency backup response team for the National
Institutes of Health (NIH). CIAC is located at the Lawrence Livermore
National Laboratory in Livermore, California. CIAC is also a founding
member of FIRST, the Forum of Incident Response and Security Teams, a
global organization established to foster cooperation and coordination
among computer security teams worldwide.

CIAC services are available to DOE, DOE contractors, and the NIH. CIAC
can be contacted at:
    Voice:    +1 925-422-8193 (7x24)
    FAX:      +1 925-423-8002
    STU-III:  +1 925-423-2604
    E-mail:   ciac@ciac.org

Previous CIAC notices, anti-virus software, and other information are
available from the CIAC Computer Security Archive.

   World Wide Web:      http://www.ciac.org/
   Anonymous FTP:       ftp.ciac.org

PLEASE NOTE: Many users outside of the DOE, ESnet, and NIH computing
communities receive CIAC bulletins.  If you are not part of these
communities, please contact your agency's response team to report
incidents. Your agency's team will coordinate with CIAC. The Forum of
Incident Response and Security Teams (FIRST) is a world-wide
organization. A list of FIRST member organizations and their
constituencies can be obtained via WWW at http://www.first.org/.

This document was prepared as an account of work sponsored by an
agency of the United States Government. Neither the United States
Government nor the University of California nor any of their
employees, makes any warranty, express or implied, or assumes any
legal liability or responsibility for the accuracy, completeness, or
usefulness of any information, apparatus, product, or process
disclosed, or represents that its use would not infringe privately
owned rights. Reference herein to any specific commercial products,
process, or service by trade name, trademark, manufacturer, or
otherwise, does not necessarily constitute or imply its endorsement,
recommendation or favoring by the United States Government or the
University of California. The views and opinions of authors expressed
herein do not necessarily state or reflect those of the United States
Government or the University of California, and shall not be used for
advertising or product endorsement purposes.

LAST 10 CIAC BULLETINS ISSUED (Previous bulletins available from CIAC)

N-065: Multiple Vulnerabilities in Lotus Notes and Domino
N-066: RealPlayer PNG Deflate Heap Corruption Vulnerability
N-067: Sendmail MTA Buffer Overflow Vulnerability
N-068: Sun Solaris Buffer Overflow in lpq(1B) Command
N-069: Sun Solaris newtask(1) Command Vulnerability
N-070: Sun Solaris at(1) Command Vulnerability
N-071: Red Hat Eye of GNOME (EOG) Packages Fix Format String Vulnerability
N-072: Sun Solaris dtsession Security Vulnerability
N-073: Samba 'call_trans2open' Remote Buffer Overflow Vulnerability
N-074: Microsoft Virtual Machine (VM) Vulnerability


TUCoPS is optimized to look best in Firefox® on a widescreen monitor (1440x900 or better).
Site design & layout copyright © 1986-2024 AOH