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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                sendmail
        Announcement ID:        SUSE-SA:2006:017
        Date:                   Wed, 22 Mar 2006 17:00:00 +0000
        Affected Products:      SUSE LINUX 10.0
                                SUSE LINUX 9.3
                                SUSE LINUX 9.2
                                SUSE LINUX 9.1
                                SuSE Linux Enterprise Server 8
                                SUSE SLES 9
                                UnitedLinux 1.0
        Vulnerability Type:     remote code execution
        Severity (1-10):        9
        SUSE Default Package:   yes
        Cross-References:       CVE-2006-0058
                                VU#834865

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             sendmail remote code execution
           Problem Description
        2) Solution or Work-Around
        3) Special Instructions and Notes
        4) Package Location and Checksums
        5) Pending Vulnerabilities, Solutions, and Work-Arounds:
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   The popular MTA sendmail is vulnerable to a race condition when handling
   signals.
   Under certain circumstances this bug can be exploited by an attacker to
   execute commands remotely.
   
   Sendmail was the default MTA in SuSE Linux Enterprise Server 8. Later
   products use postfix as MTA.
   
   Thanks to Mark Dowd who found this bug.

2) Solution or Work-Around

   There is no work-around known.

3) Special Instructions and Notes

   Please restart sendmail after the update.

4) Package Location and Checksums

   The preferred method for installing security updates is to use the YaST
   Online Update (YOU) tool. YOU detects which updates are required and
   automatically performs the necessary steps to verify and install them.
   Alternatively, download the update packages for your distribution manually
   and verify their integrity by the methods listed in Section 6 of this
   announcement. Then install the packages using the command

     rpm -Fhv 

   to apply the update, replacing  with the filename of the
   downloaded RPM package.

   
   x86 Platform:
   
   SUSE LINUX 10.0:
             06ab5c69929cb50f26f54588f66146b4
   
   SUSE LINUX 9.3:
             df6e12d411035bf7ab3ad996f92ac5cf
   
   SUSE LINUX 9.2:
             17c91fd6341147c689dc2cd7dc71d911
   
   SUSE LINUX 9.1:
             157dfa4779aff534e835215492697cbb
   
   Power PC Platform:
   
   SUSE LINUX 10.0:
             12dc596559ab135dcc338d5783052fa3
   
   x86-64 Platform:
   
   SUSE LINUX 10.0:
             ef97f8861a09194962a73822cc9fc046
   
   SUSE LINUX 9.3:
             a3d0e0ee376a474039b03bcc4b5bf424
   
   SUSE LINUX 9.2:
             ade99a91173e0cc39d0c64c259bc7f33
   
   SUSE LINUX 9.1:
             14e8a55656f88e11a50d732379491922
   
   Sources:
   
   SUSE LINUX 10.0:
             94722f948da4436d9b32abf3df26486d
   
   SUSE LINUX 9.3:
             e75f7eb0d5aad94141e06a57701f8aa7
   
   SUSE LINUX 9.2:
             30ea81965aafb0e7726c7c503ae6838a
   
   SUSE LINUX 9.1:
             9fb0bc7806b56efe1049595cf3dbdd95
             15db49b697c161e35c06115e352de985
   
   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:
   
   
______________________________________________________________________________

5) Pending Vulnerabilities, Solutions, and Work-Arounds:

   Please read our weekly summary advisory.
______________________________________________________________________________

6) Authenticity Verification and Additional Information

  - Announcement authenticity verification:

    SUSE security announcements are published via mailing lists and on Web
    sites. The authenticity and integrity of a SUSE security announcement is
    guaranteed by a cryptographic signature in each announcement. All SUSE
    security announcements are published with a valid signature.

    To verify the signature of the announcement, save it as text into a file
    and run the command

      gpg --verify 

    replacing  with the name of the file where you saved the
    announcement. The output for a valid signature looks like:

      gpg: Signature made  using RSA key ID 3D25D3D9
      gpg: Good signature from "SuSE Security Team "

    where  is replaced by the date the document was signed.

    If the security team's key is not contained in your key ring, you can
    import it from the first installation CD. To import the key, use the
    command

      gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc

  - Package authenticity verification:

    SUSE update packages are available on many mirror FTP servers all over the
    world. While this service is considered valuable and important to the free
    and open source software community, the authenticity and the integrity of
    a package needs to be verified to ensure that it has not been tampered
    with.

    There are two verification methods that can be used independently from
    each other to prove the authenticity of a downloaded file or RPM package:

    1) Using the internal gpg signatures of the rpm package
    2) MD5 checksums as provided in this announcement

    1) The internal rpm package signatures provide an easy way to verify the
       authenticity of an RPM package. Use the command

        rpm -v --checksig 

       to verify the signature of the package, replacing  with the
       filename of the RPM package downloaded. The package is unmodified if it
       contains a valid signature from build@suse.de with the key ID 9C800ACA.

       This key is automatically imported into the RPM database (on
       RPMv4-based distributions) and the gpg key ring of 'root' during
       installation. You can also find it on the first installation CD and at
       the end of this announcement.

    2) If you need an alternative means of verification, use the md5sum
       command to verify the authenticity of the packages. Execute the command

         md5sum 

       after you downloaded the file from a SUSE FTP server or its mirrors.
       Then compare the resulting md5sum with the one that is listed in the
       SUSE security announcement. Because the announcement containing the
       checksums is cryptographically signed (by security@suse.de), the
       checksums show proof of the authenticity of the package if the
       signature of the announcement is valid. Note that the md5 sums
       published in the SUSE Security Announcements are valid for the
       respective packages only. Newer versions of these packages cannot be
       verified.

  - SUSE runs two security mailing lists to which any interested party may
    subscribe:

    suse-security@suse.com
        -   General Linux and SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    suse-security-announce@suse.com
        -   SUSE's announce-only mailing list.
            Only SUSE's security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    For general information or the frequently asked questions (FAQ),
    send mail to  or
    .

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================