-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                sendmail
        Announcement ID:        SUSE-SA:2006:032
        Date:                   Wed, 14 Jun 2006 19:00:00 +0000
        Affected Products:      SUSE LINUX 10.1
                                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 denial of service
        Severity (1-10):        5
        SUSE Default Package:   no
        Cross-References:       CVE-2006-1173, VU#146718

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

______________________________________________________________________________

1) Problem Description and Brief Discussion

   The Mail Transfer Agent sendmail has a remote exploitable problem,
   where a specially crafted MIME messages can crash sendmail and block
   queue processing.

   This issue is tracked by the Mitre CVE ID CVE-2006-1173 and CERT
   VU#146718.

2) Solution or Work-Around

   There is no known workaround, please install the update packages.

3) Special Instructions and Notes

   Please close and restart all running instances of 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.1:
             1e3fa1b7a729d2b260a4da6d9ff962f4

   SUSE LINUX 10.0:
             70a41db80164fb7d50e823774566ea9e

   SUSE LINUX 9.3:
             94679162ea3b479f20362f0d01ea4d72

   SUSE LINUX 9.2:
             10e79f3a40ec0c25911cf2549009d609

   SUSE LINUX 9.1:
             adc59ac9fa4ba76743bd073e0334b9d9

   Power PC Platform:

   SUSE LINUX 10.1:
             81580c25511daa9862a1dd8f5ca7d48b

   SUSE LINUX 10.0:
             ff81143d1dee29c58aea6038a952c903

   x86-64 Platform:

   SUSE LINUX 10.1:
             8f724bcf3c0aaac8923241c9f3288c40

   SUSE LINUX 10.0:
             40fc8a5f7ad12159528b8cc1d4c2173f

   SUSE LINUX 9.3:
             d8b8ba804ac1a04b22d673c52d654f69

   SUSE LINUX 9.2:
             6dcf297dbbcfb5d2b7d0a55efb9c3099

   SUSE LINUX 9.1:
             dd3ed5bd5318928a9bfe4320eed67027

   Sources:

   SUSE LINUX 10.1:
             7ed5b46eb2ed2a18becadf43b8cba7b1

   SUSE LINUX 10.0:
             0f93d3d608305d44667ec1b35a76e626

   SUSE LINUX 9.3:
             c9ac83c770a63f94fe18a156898ffe70

   SUSE LINUX 9.2:
             6dd980cf9e4ee2d14d9ec1e8f7c804f5

   SUSE LINUX 9.1:
             d312bd0544a7e3b7456abfb79a296383
             c1bfd5c0dbd95faee42ae0a2694147bf

   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:

   UnitedLinux 1.0
     
   SUSE SLES 9
     
   SuSE Linux Enterprise Server 8
     
______________________________________________________________________________

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

   See SUSE Security Summary Report.
______________________________________________________________________________

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