TUCoPS :: SGI :: ciacj012.txt

SGI Irix Routed Vulnerability



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

                             INFORMATION BULLETIN

                       SGI IRIX routed(1M) Vulnerability

October 26, 1998 18:00 GMT                                        Number J-012
PROBLEM:       A vulnerability has been identified in the routed(1M) daemon
               which is used to manage network routing tables.
PLATFORM:      IRIX 3.x, 4.x, 5.0.x, 5.1.x, 5.2, 5.3, 6.0.x, 6.1, 6.2, 6.3,
DAMAGE:        If exploited, a malicious user may append routed(1M) debug and
               tracing information to arbitrary files on the system.
SOLUTION:      Disable the routed(1M) daemon until patches can be installed.
VULNERABILITY  Risk is high. A local account is not needed to exploit this
ASSESSMENT:    vulnerability, it can be exploited remotely by using carefully
               crafted network packets. This vulnerability has been publicly
               discussed in Usenet newsgroups and mailing list.

[  Start Silicon Graphics Inc. Advisory ]


                Silicon Graphics Inc. Security Advisory

        Title:   IRIX routed(1M) Vulnerability
        Number:  19981004-01-PX
        Date:    October 21, 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 routed(1M) daemon is used to manage network routing tables.

A vulnerability has been discovered in routed(1M) which allows a malicious
user to append debug and tracing information to arbitrary files on 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 has been corrected in future releases of IRIX.

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

The routed(1M) daemon is installed by default on IRIX.

A local account is not needed in order to exploit this vulnerability.

The vulnerability can be exploited remotely by using carefully crafted network

The vulnerability allows a malicious user to append routed(1M) debug tracing
information to arbitrary files on the system.

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

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

There are no workarounds for this routed(1M) vulnerability. The routed(1M)
daemon must be disabled or patches installed.

The steps below can be used to disable the routed(1M) daemon to prevent
exploitation of this vulnerability until patches can be installed.

      **** WARNING ****

      Disabling routed(1M) daemon will prevent dynamic updates of the
      network routing tables. Static routes must be configured, see the
      route(1M) man page for more information.

     1) Become the root user on the system.

               % /bin/su -

     2) Verify routed(1M) daemon is enabled.

              # chkconfig

              Flag                 State
              ====                 =====
              routed               on

     3) Disable routed(1M) daemon.

              # chkconfig routed off

     4) Verify routed(1M) daemon has been disabled.

              # chkconfig

              Flag                 State
              ====                 =====
              routed               off

     5) Stop and restart all system networking daemons.

              # /etc/init.d/network stop;/etc/init.d/network start

     6) Return to previous user level.

                # exit

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

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

   IRIX 3.x          yes          not avail    Note 1
   IRIX 4.x          yes          not avail    Note 1
   IRIX 5.0.x        yes          not avail    Note 1
   IRIX 5.1.x        yes          not avail    Note 1
   IRIX 5.2          yes          not avail    Note 1
   IRIX 5.3          yes           2770
   IRIX 6.0.x        yes          not avail    Note 1
   IRIX 6.1          yes          not avail    Note 1
   IRIX 6.2          yes           1638        Note 2
   IRIX 6.3          yes           2413        Note 2
   IRIX 6.4          yes           2413        Note 2
   IRIX 6.5          no
   IRIX 6.5          no
   IRIX 6.5.1        no


     1) Upgrade to currently supported IRIX operating system.
     2) These are the base patches where the security issue was first fixed.
        There may be newer rollup patches that contain the security fix and
        are currently available from http://support.sgi.com/ or you SGI
        support provider.

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

The primary SGI anonymous FTP site for security information and patches
is sgigate.sgi.com ( Security information and patches can be
found in the ~ftp/security and ~ftp/patches directories, respectively.

For security and patch management reasons, ftp.sgi.com (mirror of sgigate)
behind and does not do a real-time update of ~ftp/security and ~ftp/patches

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

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

Filename:                 README.patch.1638
Algorithm #1 (sum -r):    25810 10 README.patch.1638
Algorithm #2 (sum):       45994 10 README.patch.1638
MD5 checksum:             5CFFC234C3FD6A55AAF1724A23856464

Filename:                 patchSG0001638
Algorithm #1 (sum -r):    54461 3 patchSG0001638
Algorithm #2 (sum):       10118 3 patchSG0001638
MD5 checksum:             1A4F38FCB51AEA8444236CD0B78EE8BB

Filename:                 patchSG0001638.eoe_hdr
Algorithm #1 (sum -r):    10008 8 patchSG0001638.eoe_hdr
Algorithm #2 (sum):       23343 8 patchSG0001638.eoe_hdr
MD5 checksum:             960162CA99A3F2B00C1F2728F1FD82A8

Filename:                 patchSG0001638.eoe_man
Algorithm #1 (sum -r):    25386 52 patchSG0001638.eoe_man
Algorithm #2 (sum):       5077 52 patchSG0001638.eoe_man
MD5 checksum:             ECA70503EEB12265CB56CC1CBA0AAB74

Filename:                 patchSG0001638.eoe_sw
Algorithm #1 (sum -r):    04406 241 patchSG0001638.eoe_sw
Algorithm #2 (sum):       3325 241 patchSG0001638.eoe_sw
MD5 checksum:             123CA06F9A5B91D1D56458FF455538C4

Filename:                 patchSG0001638.idb
Algorithm #1 (sum -r):    18065 4 patchSG0001638.idb
Algorithm #2 (sum):       22105 4 patchSG0001638.idb
MD5 checksum:             E8333BC62A89A6C4A2326F9C9089565A

Algorithm #1 (sum -r):    59269 9 README.patch.2413
Algorithm #2 (sum):       61782 9 README.patch.2413
MD5 checksum:             81A1CC8326C35FC9D8A36E6E4C2ECE7E

Filename:                 patchSG0002413
Algorithm #1 (sum -r):    35882 3 patchSG0002413
Algorithm #2 (sum):       14583 3 patchSG0002413
MD5 checksum:             ADD49D668CDF3644CB80AEE1B5EC530F

Filename:                 patchSG0002413.eoe_hdr
Algorithm #1 (sum -r):    43690 8 patchSG0002413.eoe_hdr
Algorithm #2 (sum):       23342 8 patchSG0002413.eoe_hdr
MD5 checksum:             B88588DEC32FB32AEB2F8420BC7E172E

Filename:                 patchSG0002413.eoe_man
Algorithm #1 (sum -r):    34349 39 patchSG0002413.eoe_man
Algorithm #2 (sum):       52356 39 patchSG0002413.eoe_man
MD5 checksum:             4CA92E9BDF2FD32354CE3F640B69BA75

Filename:                 patchSG0002413.eoe_sw
Algorithm #1 (sum -r):    44812 216 patchSG0002413.eoe_sw
Algorithm #2 (sum):       33076 216 patchSG0002413.eoe_sw
MD5 checksum:             6CC82F0698061F49686FADCB7C27D97F

Filename:                 patchSG0002413.idb
Algorithm #1 (sum -r):    19469 3 patchSG0002413.idb
Algorithm #2 (sum):       44128 3 patchSG0002413.idb
MD5 checksum:             F8B97D25D2C386CB3DF9C67940B39D7E

Filename:                 README.patch.2770
Algorithm #1 (sum -r):    50674 54 README.patch.2770
Algorithm #2 (sum):       55165 54 README.patch.2770
MD5 checksum:             AF52BE0D11D1ABA533F750808B7C6976

Filename:                 patchSG0002770
Algorithm #1 (sum -r):    45021 29 patchSG0002770
Algorithm #2 (sum):       38712 29 patchSG0002770
MD5 checksum:             8E458BF95BB806D5082D36F5C323C3AD

Filename:                 patchSG0002770.dev_hdr
Algorithm #1 (sum -r):    55046 18 patchSG0002770.dev_hdr
Algorithm #2 (sum):       21666 18 patchSG0002770.dev_hdr
MD5 checksum:             12D756C9AAADDA464F628FB08B8012C2

Filename:                 patchSG0002770.eoe1_man
Algorithm #1 (sum -r):    58486 19 patchSG0002770.eoe1_man
Algorithm #2 (sum):       19828 19 patchSG0002770.eoe1_man
MD5 checksum:             971A700918352743FDFAD9DC7AAC7F08

Filename:                 patchSG0002770.eoe1_sw
Algorithm #1 (sum -r):    19070 3874 patchSG0002770.eoe1_sw
Algorithm #2 (sum):       2196 3874 patchSG0002770.eoe1_sw
MD5 checksum:             BAC859508D8025C05CF7EF8732E8C340

Filename:                 patchSG0002770.eoe2_man
Algorithm #1 (sum -r):    20509 16 patchSG0002770.eoe2_man
Algorithm #2 (sum):       64242 16 patchSG0002770.eoe2_man
MD5 checksum:             B0491FEFB0CE1C0BC03F7A1345BDE250

Filename:                 patchSG0002770.eoe2_sw
Algorithm #1 (sum -r):    35898 1681 patchSG0002770.eoe2_sw
Algorithm #2 (sum):       50094 1681 patchSG0002770.eoe2_sw
MD5 checksum:             009D8A477E83CE4646F004FB3F48953E

Filename:                 patchSG0002770.idb
Algorithm #1 (sum -r):    46255 53 patchSG0002770.idb
Algorithm #2 (sum):       6566 53 patchSG0002770.idb
MD5 checksum:             8A53DCAFC6BF0E8A4682D74733834C18

Filename:                 patchSG0002770.nfs_man
Algorithm #1 (sum -r):    22345 17 patchSG0002770.nfs_man
Algorithm #2 (sum):       21111 17 patchSG0002770.nfs_man
MD5 checksum:             8782FA52CAB650472352DABC1C38B823

Filename:                 patchSG0002770.nfs_sw
Algorithm #1 (sum -r):    22859 162 patchSG0002770.nfs_sw
Algorithm #2 (sum):       7001 162 patchSG0002770.nfs_sw
MD5 checksum:             BA848F9526D84CF205C7DD080CF7D46E

- --------------------------
- ----- 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 Silicon Graphics Inc. Advisory ]

CIAC wishes to acknowledge the contributions of Silicon Graphics Inc. 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
    FAX:      +1 925-423-8002
    STU-III:  +1 925-423-2604
    E-mail:   ciac@llnl.gov

For emergencies and off-hour assistance, DOE, DOE contractor sites,
and the NIH may contact CIAC 24-hours a day. During off hours (5PM -
8AM PST), call the CIAC voice number 925-422-8193 and leave a message,
or call 800-759-7243 (800-SKY-PAGE) to send a Sky Page. CIAC has two
Sky Page PIN numbers, the primary PIN number, 8550070, is for the CIAC
duty person, and the secondary PIN number, 8550074 is for the CIAC
Project Leader.

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

   World Wide Web:      http://www.ciac.org/
                        (or http://ciac.llnl.gov -- they're the same machine)
   Anonymous FTP:       ftp.ciac.org
                        (or ciac.llnl.gov -- they're the same machine)
   Modem access:        +1 (925) 423-4753 (28.8K baud)
                        +1 (925) 423-3331 (28.8K baud)

CIAC has several self-subscribing mailing lists for electronic
1. CIAC-BULLETIN for Advisories, highest priority - time critical
   information and Bulletins, important computer security information;
2. SPI-ANNOUNCE for official news about Security Profile Inspector
   (SPI) software updates, new features, distribution and
3. SPI-NOTES, for discussion of problems and solutions regarding the
   use of SPI products.

Our mailing lists are managed by a public domain software package
called Majordomo, which ignores E-mail header subject lines. To
subscribe (add yourself) to one of our mailing lists, send the
following request as the E-mail message body, substituting
ciac-bulletin, spi-announce OR spi-notes for list-name:

E-mail to       ciac-listproc@llnl.gov or majordomo@tholia.llnl.gov:
        subscribe list-name
  e.g., subscribe ciac-bulletin

You will receive an acknowledgment email immediately with a confirmation
that you will need to mail back to the addresses above, as per the
instructions in the email.  This is a partial protection to make sure
you are really the one who asked to be signed up for the list in question.

If you include the word 'help' in the body of an email to the above address,
it will also send back an information file on how to subscribe/unsubscribe,
get past issues of CIAC bulletins via email, etc.

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)

J-002: SGI IRIX Mail(1)/mailx(1) Security Vulnerabilities
J-003: SGI IRIX On-Line Customer Registration Vulnerabilities
J-004: SunOS ftp client Vulnerability
J-005: SGI IRIX at(1) Vulnerability
J-006: NFS mountd Buffer Overflow Vulnerability
J-007: HP OpenView Omniback II Vulnerability
J-008: FreeBSD TCP RST Denial of Service Vulnerability
J-009: Cisco IOS Command History Release at Login Prompt
J-010: SGI Buffer Overflow Vulnerabilities ( xterm(1), Xaw library)
J-011: Microsoft IE 4.01 Untrusted Scripted Paste (Cuartango Vul.)

Version: 4.0 Business Edition


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