AUSCERT External Security Bulletin Redistribution

                   ESB-2001.451 -- SGI Security Advisory
                          IRIX IGMP vulnerability
                              25 October 2001


        AusCERT Security Bulletin Summary

Product:                IRIX
Vendor:                 SGI
Impact:                 Denial of Service
Access Required:        Remote

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


                          SGI Security Advisory

        Title:   IRIX IGMP vulnerability
        Number:  20011001-01-P
        Date:    October 22, 2001
   Reference:    CVE Pending (Advisory will be updated upon receipt of CVE)

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

A malformed IGMP multicast packet under specific conditions can cause
SGI systems running the IRIX operating system to panic.

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

SGI systems running the IRIX operating system that are connected
to a network are vulnerable.

A local user account on the vulnerable system is not required
in order to exploit this issue.

The vulnerability can be exploited remotely over an untrusted network.

The vulnerability can lead to a denial of service attack.

This network kernel vulnerability has been publicly discussed in
Usenet newsgroups and security mailing lists.

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

Unfortunately, there are no immediate or temporary workarounds
that fully address this issue.  This issue can only be
fully addressed with the installation of a patch.

- - ----------------

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

   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                       Note 2
   IRIX 6.5.1        yes                       Note 2
   IRIX 6.5.2        yes                       Note 2
   IRIX 6.5.3        yes                       Note 2
   IRIX 6.5.4        yes                       Note 2
   IRIX 6.5.5        yes                       Note 2
   IRIX 6.5.6        yes                       Note 2
   IRIX 6.5.7        yes                       Note 2
   IRIX 6.5.8        yes                       Note 2
   IRIX 6.5.9        yes                       Note 2
   IRIX 6.5.10m      yes           4335        Note 2
   IRIX 6.5.10f      yes           4336        Note 2
   IRIX 6.5.11m      yes           4344        Note 2
   IRIX 6.5.11f      yes           4345        Note 2
   IRIX 6.5.12m      yes           4346        Note 2
   IRIX 6.5.12f      yes           4347        Note 2
   IRIX 6.5.13       no                        Note 4 & 5


     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) This version of the IRIX operating system is in maintenance mode.
        Upgrade to an actively supported IRIX operating system.
        See http://support.sgi.com/news/support/index.html for more

     3) Download the IRIX 6.5.13 Maintenance Release Stream from the URL:

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

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

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

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

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

Filename:                 README.patch.4335
Algorithm #1 (sum -r):    55943 7 README.patch.4335
Algorithm #2 (sum):       19062 7 README.patch.4335
MD5 checksum:             2A9905DF6959AFFE2F3CF719C74E6637

Filename:                 patchSG0004335
Algorithm #1 (sum -r):    11319 2 patchSG0004335
Algorithm #2 (sum):       37230 2 patchSG0004335
MD5 checksum:             12E9E42C0C3F91098C563D31C85BE4B5

Filename:                 patchSG0004335.eoe_sw
Algorithm #1 (sum -r):    21972 8603 patchSG0004335.eoe_sw
Algorithm #2 (sum):       46692 8603 patchSG0004335.eoe_sw
MD5 checksum:             94CAB1706EB56AAFAB9A0627D2CA39EC

Filename:                 patchSG0004335.idb
Algorithm #1 (sum -r):    03068 7 patchSG0004335.idb
Algorithm #2 (sum):       16580 7 patchSG0004335.idb
MD5 checksum:             FE3F1D724CB805BD7318C32600D2A090

Filename:                 README.patch.4336
Algorithm #1 (sum -r):    62823 7 README.patch.4336
Algorithm #2 (sum):       19060 7 README.patch.4336
MD5 checksum:             F38184632D21F94A1CA89C71D70530AC

Filename:                 patchSG0004336
Algorithm #1 (sum -r):    26584 2 patchSG0004336
Algorithm #2 (sum):       38015 2 patchSG0004336
MD5 checksum:             C1FF57323CEC2A634035F73026C9CF0E

Filename:                 patchSG0004336.eoe_sw
Algorithm #1 (sum -r):    09331 8779 patchSG0004336.eoe_sw
Algorithm #2 (sum):       3459 8779 patchSG0004336.eoe_sw
MD5 checksum:             B12E70EB833A0D66486151FCE2A74F91

Filename:                 patchSG0004336.idb
Algorithm #1 (sum -r):    23201 7 patchSG0004336.idb
Algorithm #2 (sum):       16522 7 patchSG0004336.idb
MD5 checksum:             05C88659529C30DB0D2D177FF1C327E2

Filename:                 README.patch.4344
Algorithm #1 (sum -r):    12882 7 README.patch.4344
Algorithm #2 (sum):       19081 7 README.patch.4344
MD5 checksum:             D605FA8DE9CE8FF79D4B7839C438F7C3

Filename:                 patchSG0004344
Algorithm #1 (sum -r):    54495 2 patchSG0004344
Algorithm #2 (sum):       40445 2 patchSG0004344
MD5 checksum:             5E974CD2F35263255811E87AAB208D3D

Filename:                 patchSG0004344.eoe_sw
Algorithm #1 (sum -r):    08860 8284 patchSG0004344.eoe_sw
Algorithm #2 (sum):       65368 8284 patchSG0004344.eoe_sw
MD5 checksum:             A8321587DA41E133F325734BD6015F00

Filename:                 patchSG0004344.idb
Algorithm #1 (sum -r):    52422 7 patchSG0004344.idb
Algorithm #2 (sum):       16414 7 patchSG0004344.idb
MD5 checksum:             45C54A814F605894E5F474AB67FC9163

Filename:                 README.patch.4345
Algorithm #1 (sum -r):    37957 7 README.patch.4345
Algorithm #2 (sum):       19062 7 README.patch.4345
MD5 checksum:             6C1108BFB13AD98DBD27160024F4C348

Filename:                 patchSG0004345
Algorithm #1 (sum -r):    44808 2 patchSG0004345
Algorithm #2 (sum):       41567 2 patchSG0004345
MD5 checksum:             C11F0B4E1893FE7DC99CAADEF921BD2F

Filename:                 patchSG0004345.eoe_sw
Algorithm #1 (sum -r):    11475 8466 patchSG0004345.eoe_sw
Algorithm #2 (sum):       43098 8466 patchSG0004345.eoe_sw
MD5 checksum:             0DAD073CB3E88E34AD77ABD901C04EB6

Filename:                 patchSG0004345.idb
Algorithm #1 (sum -r):    42008 6 patchSG0004345.idb
Algorithm #2 (sum):       33904 6 patchSG0004345.idb
MD5 checksum:             CCAA21B44860CC8F8802382EC1743735

Filename:                 README.patch.4346
Algorithm #1 (sum -r):    55792 7 README.patch.4346
Algorithm #2 (sum):       19105 7 README.patch.4346
MD5 checksum:             B0EF6F12900DE49BDE45DFA64C2BBE38

Filename:                 patchSG0004346
Algorithm #1 (sum -r):    31782 2 patchSG0004346
Algorithm #2 (sum):       37609 2 patchSG0004346
MD5 checksum:             F280E47CC013AB92992AEAF55B14FC1A

Filename:                 patchSG0004346.eoe_sw
Algorithm #1 (sum -r):    46823 8429 patchSG0004346.eoe_sw
Algorithm #2 (sum):       32984 8429 patchSG0004346.eoe_sw
MD5 checksum:             30ED3E381FC7780DB9157E22870287EB

Filename:                 patchSG0004346.idb
Algorithm #1 (sum -r):    31847 6 patchSG0004346.idb
Algorithm #2 (sum):       34066 6 patchSG0004346.idb
MD5 checksum:             2E297CD63A45CB49A4E121E9B78D6B4D

Filename:                 README.patch.4347
Algorithm #1 (sum -r):    55159 7 README.patch.4347
Algorithm #2 (sum):       19082 7 README.patch.4347
MD5 checksum:             FCA8B736DEA8E009AFD021C451643576

Filename:                 patchSG0004347
Algorithm #1 (sum -r):    61581 2 patchSG0004347
Algorithm #2 (sum):       38847 2 patchSG0004347
MD5 checksum:             378C742EA7DA3124F175E66FD2DDABBB

Filename:                 patchSG0004347.eoe_sw
Algorithm #1 (sum -r):    03615 8495 patchSG0004347.eoe_sw
Algorithm #2 (sum):       44129 8495 patchSG0004347.eoe_sw
MD5 checksum:             6F11752267318A41F78542F4B5DAF182

Filename:                 patchSG0004347.idb
Algorithm #1 (sum -r):    33047 6 patchSG0004347.idb
Algorithm #2 (sum):       33907 6 patchSG0004347.idb
MD5 checksum:             70C38BAF986F6442F756D70AE7D8B256

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

SGI wishes to thank the Open Source 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


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


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 INCLUDED TEXT--------------------

You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.

This security bulletin is provided as a service to AusCERT's members.  As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content.  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 may
not be updated when updates to the original are made.  If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the original authors to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above.  If you have any questions or need further
information, please contact them directly.

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.

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