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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                imap
        Announcement-ID:        SUSE-SA:2005:012
        Date:                   Tue, 1 Mar 2005 10:00:00 +0000
        Affected products:      8.2, 9.0, 9.1, 9.2
                                SUSE Linux Enterprise Server 8, 9
        Vulnerability Type:     remote authentication bypass
        Severity (1-10):        6
        SUSE default package:   no
        Cross References:       CAN-2005-0198

    Content of this advisory:
        1) security vulnerability resolved:
             CRAM-MD5 authentication bug
           problem description
        2) solution/workaround
        3) special instructions and notes
        4) package location and checksums
        5) pending vulnerabilities, solutions, workarounds:
            See SUSE Security Summary Report.
        6) standard appendix (further information)

______________________________________________________________________________

1) problem description, brief discussion

    The University of Washington imap daemon can be used to access mails
    remotely using the IMAP protocol.
    
    This update fixes a logical error in the challenge response
    authentication mechanism CRAM-MD5 used by UW IMAP. Due to this
    mistake a remote attacker can gain access to the IMAP server as
    arbitrary user.

    This is tracked by the Mitre CVE ID CAN-2005-0198.

2) solution/workaround

    None, please install the updated packages.

3) special instructions and notes

    None.

4) package location and checksums

    Please download the update package for your distribution and verify its
    integrity by the methods listed in section 3) of this announcement.
    Then, install the package using the command "rpm -Fhv file.rpm" to apply
    the update.
    Our maintenance customers are being notified individually. The packages
    are being offered to install from the maintenance web.

    
    x86 Platform:
    
    SUSE Linux 9.2:
               2b4cf0f70fb0164a90f6e73b66f28c5a
    
    SUSE Linux 9.1:
               32eb45928cf31bb0cbae78139303561b
    
    SUSE Linux 9.0:
               b8af4a9008cb1d311f650700b6d642c5
    
    SUSE Linux 8.2:
               6f73b1197b2a095fc30b8afde860f5fe
    
    x86-64 Platform:
    
    SUSE Linux 9.2:
               a6a79a3e1459dd1d5799e40257684d4e
    source rpm(s):
               18201a6f78b73d2250f6ea0e614049b2
    
    SUSE Linux 9.1:
               007c9777aacc36dec72067cf6ac39e7d
    source rpm(s):
               9bf8dda300636e712f164d784bc131a5
    
    SUSE Linux 9.0:
               25ffa1aa178c962753bc26483d0e9354
    source rpm(s):
               2da3ea9899a1ddf909d7dc5059138e7d


______________________________________________________________________________

5)  Pending vulnerabilities in SUSE Distributions and Workarounds:

    See SUSE Security Summary Report.

______________________________________________________________________________

6)  standard appendix: authenticity verification, additional information

  - Package authenticity verification:

    SUSE update packages are available on many mirror ftp servers all over
    the world. While this service is being considered valuable and important
    to the free and open source software community, many users wish to be
    sure about the origin of the package and its content before installing
    the package. 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) md5sums as provided in the (cryptographically signed) announcement.
    2) using the internal gpg signatures of the rpm package.

    1) 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
       announcement. Since the announcement containing the checksums is
       cryptographically signed (usually using the key security@suse.de),
       the checksums show proof of the authenticity of the package.
       We disrecommend to subscribe to security lists which cause the
       email message containing the announcement to be modified so that
       the signature does not match after transport through the mailing
       list software.
       Downsides: You must be able to verify the authenticity of the
       announcement in the first place. If RPM packages are being rebuilt
       and a new version of a package is published on the ftp server, all
       md5 sums for the files are useless.

    2) 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, where  is the
       filename of the rpm package that you have downloaded. Of course,
       package authenticity verification can only target an un-installed rpm
       package file.
       Prerequisites:
        a) gpg is installed
        b) The package is signed using a certain key. The public part of this
           key must be installed by the gpg program in the directory
           ~/.gnupg/ under the user's home directory who performs the
           signature verification (usually root). You can import the key
           that is used by SUSE in rpm packages for SUSE Linux by saving
           this announcement to a file ("announcement.txt") and
           running the command (do "su -" to be root):
            gpg --batch; gpg < announcement.txt | gpg --import
           SUSE Linux distributions version 7.1 and thereafter install the
           key "build@suse.de" upon installation or upgrade, provided that
           the package gpg is installed. The file containing the public key
           is placed at the top-level directory of the first CD (pubring.gpg)
           and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de .


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

    suse-security@suse.com
        -   general/linux/SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an email 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 email to
                .

    For general information or the frequently asked questions (faq) 
    send mail to:
         or
         respectively.

    ====================================================================    SUSE's security contact is  or .
@suse.de>.
    The  public key is listed below.
    ====================================================================