SuSE Linux Advisory: cyrus-imapd

____________________________________________________________________________

                        SuSE Security Announcement

        Package:                cyrus-imapd
        Announcement-ID:        SuSE-SA:2002:048
        Date:                   Fri Dec 20 18:00:00 MET 2002
        Affected products:      7.1, 7.2, 7.3, 8.0, 8.1,
                                SuSE eMail Server III, 3.1,
                                SuSE Linux Connectivity Server,
                                SuSE Linux Enterprise Server 7,
                                SuSE Linux Enterprise Server 8,
                                SuSE Linux Office Server,
                                SuSE Linux Openexchange Server 4
        Vulnerability Type:     remote command execution
        Severity (1-10):        6
        SuSE default package:   no
        Cross References:       -

    Content of this advisory:
        1) security vulnerability resolved: Buffer overflows in cyrus-imapd.
           problem description, discussion, solution and upgrade information
        2) pending vulnerabilities, solutions, workarounds:
            - MySQL
            - traceroute
            - CUPS
            - imap-2000c
        3) standard appendix (further information)

____________________________________________________________________________

1)  problem description, brief discussion, solution, upgrade information

    The cyrus imapd contains a buffer overflow which could be exploited
    by remote attackers prior to logging in. Attackers could generate oversized
    error messages and overflow buffers inside imapd.
      Additionally to this fix, an overflow in the SASL library (as used by the
    cyrus imapd) has been fixed. This bug only affects SuSE Linux 8.1, the
    SuSE Linux Enterprise Server 8 and the SuSE Linux Openexchange Server.

    Since there is no workaround possible except shutting down the IMAP server,
    we strongly recommend an update.

    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.

    To be sure the update takes effect you have to restart the IMAP server
    by executing the following commands as root:

        /etc/rc.d/cyrus restart

    and (if using saslauthd)

        /etc/rc.d/saslauthd restart


    i386 Intel Platform:

    SuSE-8.1:
    ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/cyrus-imapd-2.1.9-41.i586.rpm
      47785bc84eeebbddcd50a267684d6500
    ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/cyrus-sasl2-2.1.7-52.i586.rpm
      b740ad1a675f2c14ffc33097a1c41ee5
    patch rpm(s):
    ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/cyrus-imapd-2.1.9-41.i586.patch.rpm
      0119fa57ef939939357dd86cd1ec1ea6
    ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/cyrus-sasl2-2.1.7-52.i586.patch.rpm
      fbf3bad7c6542e45d699c0d69b0798c0
    source rpm(s):
    ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/cyrus-imapd-2.1.9-41.src.rpm
      a51f1b81249cad5e48e5d05535ae2ab8
    ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/cyrus-sasl2-2.1.7-52.src.rpm
      98cba687c3d2c89761cc6e9b34cd7e71

    SuSE-8.0:
    ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/cyrus-imapd-2.0.16-361.i386.rpm
      3dd8c8c26753cddb56f9adb2e0a352fe
    patch rpm(s):
    ftp://ftp.suse.com/pub/suse/i386/update/8.0/n4/cyrus-imapd-2.0.16-361.i386.patch.rpm
      612e6f1652c536b316a6a480389dc729
    source rpm(s):
    ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/cyrus-imapd-2.0.16-361.src.rpm
      7c4cd098d4c96726fc2ed21597a8ae3c

    SuSE-7.3:
    ftp://ftp.suse.com/pub/suse/i386/update/7.3/n2/cyrus-imapd-2.0.16-361.i386.rpm
      bd294c4539c895d16ff11fc8298a6c44
    source rpm(s):
    ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/cyrus-imapd-2.0.16-361.src.rpm
      689bd12bc2fefc627dd13b45cca68922

    SuSE-7.2:
    ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/cyrus-imapd-2.0.16-362.i386.rpm
      feb98be591cd938dee6fbff1b09e11d0
    source rpm(s):
    ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/cyrus-imapd-2.0.16-362.src.rpm
      2beb58cb743a0923cefbceccea871df2

    SuSE-7.1:
    ftp://ftp.suse.com/pub/suse/i386/update/7.1/n2/cyrus-imapd-2.0.12-69.i386.rpm
      61f850212a2d2ae72a7446df3b96e891
    source rpm(s):
    ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/cyrus-imapd-2.0.12-69.src.rpm
      77252f38facbbde01839e817a2f0514d


    Sparc Platform:

    SuSE-7.3:
    ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n2/cyrus-imapd-2.0.16-58.sparc.rpm
      093642ae51cad7a03660ea5b89dd533e
    source rpm(s):
    ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/cyrus-imapd-2.0.16-58.src.rpm
      4e1bc8e98e61918cce6976c7c373bc53


    AXP Alpha Platform:

    SuSE-7.1:
    ftp://ftp.suse.com/pub/suse/axp/update/7.1/n2/cyrus-imapd-2.0.12-24.alpha.rpm
      4194ee9cc379d0d8448029480c7b36b3
    source rpm(s):
    ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/cyrus-imapd-2.0.12-24.src.rpm
      08ab826ab71a531bb51c12b7fed19919


    PPC Power PC Platform:

    SuSE-7.3:
    ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n2/cyrus-imapd-2.0.16-208.ppc.rpm
      3d57fefb8f9d23a6e863652f148fd4ff
    source rpm(s):
    ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/cyrus-imapd-2.0.16-208.src.rpm
      4e883ee340e061c948c1835aff15e50b

    SuSE-7.1:
    ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n2/cyrus-imapd-2.0.12-32.ppc.rpm
      d518ece0e01cf731ab2d19c73c82a2de
    source rpm(s):
    ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/cyrus-imapd-2.0.12-32.src.rpm
      d61b35b30f5704194506ec1238f741bf


____________________________________________________________________________

2)  Pending vulnerabilities in SuSE Distributions and Workarounds:

    - MySQL
    Stefan Esser from e-matters discovered security critical bugs in the
    MySQL server and client libraries. New packages are currently being built
    and will soon be available. We will inform you with a separate advisory
    when all packages for all platforms are available.

    - traceroute
    The recent update for the traceroute package did not fix all overflows
    properly. New packages have been prepared and should already be available
    on our ftp servers. The newly found bugs are not critical since the last
    update for traceroute drops the superuser privileges before the overflow
    can be triggered. However since the attacker could gain access to a raw
    socket upon successfull exploitation, an update is recommended.

    - CUPS
    iDEFENSE reported various bugs in the CUPS printing system. These bugs could
    lead to a remote compromise of the system. New packages are already available
    on our ftp servers. We will inform you with a separate advisory when all
    packages for all platforms are available.

    - imap-2000c
    The IMAP implementation of the University of Washington contained a buffer
    overflow. This overflow happens after the authentication phase, so only
    remote attackers with a valid IMAP account can exploit this bug. They will
    obtain a shell with their user privileges if exploited properly. ;-)
    Only versions less or eqal to imap-2000c (as shipped up to SL 7.3) are
    affected.
      The author of this imapd does not offer patches for older versions but
    rather suggests to use the newest version available at
    ftp://ftp.cac.washington.edu/mail/imap.tar.Z
    Due to the habbit of the author and the little impact of this bug, we
    do not provide patched pre-build packages.


____________________________________________________________________________

3)  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 <name-of-the-file.rpm>
       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 [email protected]),
       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 <file.rpm>
       to verify the signature of the package, where <file.rpm> 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 "[email protected]" 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:

    [email protected]
        -   general/linux/SuSE security discussion.
            All SuSE security announcements are sent to this list.
            To subscribe, send an email to
                <[email protected]>.

    [email protected]
        -   SuSE's announce-only mailing list.
            Only SuSE's security announcements are sent to this list.
            To subscribe, send an email to
                <[email protected]>.

    For general information or the frequently asked questions (faq)
    send mail to:
        <[email protected]> or
        <[email protected]> respectively.

    =====================================================================
    SuSE's security contact is <[email protected]> or <[email protected]>.
    The <[email protected]> public key is listed below.
    =====================================================================
____________________________________________________________________________

    The information in this advisory may be distributed or reproduced,
    provided that the advisory is not modified in any way. In particular,
    it is desired that the clear-text signature shows proof of the
    authenticity of the text.
    SuSE Linux AG makes no warranties of any kind whatsoever with respect
    to the information contained in this security advisory.

Type Bits/KeyID    Date       User ID
pub  2048R/3D25D3D9 1999-03-06 SuSE Security Team <[email protected]>
pub  1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <[email protected]>

- -----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org