lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <Pine.SGI.4.51.0304021333420.413286@einstein.csd.sgi.com>
From: agent99 at sgi.com (SGI Security Coordinator)
Subject: Sendmail parseaddr security vulnerability on IRIX

-----BEGIN PGP SIGNED MESSAGE-----

______________________________________________________________________________
                          SGI Security Advisory

Title    : Sendmail parseaddr security vulnerability
Number   : 20030401-01-P
Date     : April 2, 2003
Reference: CERT CA-2003-12
Reference: CERT VU#897604
Reference: CVE CAN-2003-0161
Reference: SGI BUG 886104
Fixed in : IRIX 6.5.20 or patches 5045 and 5046
______________________________________________________________________________

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

It's been reported that there is a vulnerability in Sendmail versions 8.12.8
and prior. The address parser performs insufficient bounds checking in
certain conditions due to a char to int conversion, making it possible for
an attacker to take control of the application.  This vulnerability may be
exploited by a remote attacker, no local account is required.  It may be
possible to gain root access through this vulnerability.

See the following:

  http://lists.netsys.com/pipermail/full-disclosure/2003-March/008973.html
  http://www.cert.org/advisories/CA-2003-12.html
  http://www.sendmail.org/8.12.9.html
  http://www.kb.cert.org/vuls/id/897604

for additional information.

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 sendmail 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.19f

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

At this time, there is no effective workaround (other than disabling
sendmail) for these problems.  SGI recommends either upgrading to IRIX
6.5.20, 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            5045       Notes 2, 4, 5, and 7
   IRIX 6.5.16       yes            5045       Notes 2, 4, 5, and 7
   IRIX 6.5.17       yes            5045       Notes 2, 4, 5, and 7
   IRIX 6.5.18       yes            5045       Notes 2, 4, 5, and 7
   IRIX 6.5.19       yes            5046       Notes 2, and 4-7
   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

     4) Install the patch.  Note that the patches don't actually upgrade
        the version # of sendmail, but do contain the fixes.

     5) This patch also fixes the smrsh issue discussed in SGI Security
        Bulletin 20030101-01-P.

     6) This patch also fixes the relaying issue discussed in SGI Security
        Bulletin 20030101-01-P.

     7) This patch also fixes the remote buffer overflow issue discussed in
        SGI Security Advisory 20030301-01-P.

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

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

Filename:                 README.patch.5045
Algorithm #1 (sum -r):    17058 9 README.patch.5045
Algorithm #2 (sum):       29710 9 README.patch.5045
MD5 checksum:             2A11FB27058D75290D57687B128F0731

Filename:                 patchSG0005045
Algorithm #1 (sum -r):    25641 5 patchSG0005045
Algorithm #2 (sum):       25640 5 patchSG0005045
MD5 checksum:             4D63C59F6CDFDB3AAB7E3D337890D037

Filename:                 patchSG0005045.eoe_src
Algorithm #1 (sum -r):    19317 302 patchSG0005045.eoe_src
Algorithm #2 (sum):       12694 302 patchSG0005045.eoe_src
MD5 checksum:             870AB3F3367587C6027EDA08988B5DDF

Filename:                 patchSG0005045.eoe_sw
Algorithm #1 (sum -r):    39041 664 patchSG0005045.eoe_sw
Algorithm #2 (sum):       49516 664 patchSG0005045.eoe_sw
MD5 checksum:             5EA5D446929D0F2883FC50DDA66FF301

Filename:                 patchSG0005045.idb
Algorithm #1 (sum -r):    26055 4 patchSG0005045.idb
Algorithm #2 (sum):       29470 4 patchSG0005045.idb
MD5 checksum:             74EF204CA7A672387C027D5AC1D71EAB

Filename:                 README.patch.5046
Algorithm #1 (sum -r):    08295 9 README.patch.5046
Algorithm #2 (sum):       31372 9 README.patch.5046
MD5 checksum:             57F117DEE0E093D6542627AB3042E492

Filename:                 patchSG0005046
Algorithm #1 (sum -r):    26132 3 patchSG0005046
Algorithm #2 (sum):       21318 3 patchSG0005046
MD5 checksum:             34947E773F7D560FA88126A9D7EB4727

Filename:                 patchSG0005046.eoe_src
Algorithm #1 (sum -r):    25109 367 patchSG0005046.eoe_src
Algorithm #2 (sum):       36323 367 patchSG0005046.eoe_src
MD5 checksum:             056CA18219771716E036242FA7E29CF1

Filename:                 patchSG0005046.eoe_sw
Algorithm #1 (sum -r):    35988 1103 patchSG0005046.eoe_sw
Algorithm #2 (sum):       42426 1103 patchSG0005046.eoe_sw
MD5 checksum:             BAA9C61B8216491FE8CE6AC0C508590B

Filename:                 patchSG0005046.idb
Algorithm #1 (sum -r):    35518 4 patchSG0005046.idb
Algorithm #2 (sum):       7374 4 patchSG0005046.idb
MD5 checksum:             42BFA979BB5F0327CF329CDD21033972


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


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

SGI wishes to thank Michal Zalewski, sendmail.org and the users of the
Internet 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
security-info@....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 (216.32.174.211).  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@....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@....com
subscribe wiretap <YourEmailAddress>
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@....com.

For reporting *NEW* SGI security issues, email can be sent to
security-alert@....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

iQCVAwUBPotWYbQ4cFApAP75AQH5DgP/Xe+S6v4aStNTcMX/gdMJwJt2Mai8GkPG
L0bmJcx644qzrHrHy/+/RZpnRxNWX3SETgJLwxAHBbBre23w6IeQ88jW19ZkEoj0
rRf2LwiZC1Zm/Ra9zb4tF2QFvWRXgzErcFRvRccKb48i1yPDCKZov2KUBUwnXZ/h
r8uMyqw8TYI=
=vBwE
-----END PGP SIGNATURE-----

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ