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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                openslp
        Announcement-ID:        SUSE-SA:2005:015
        Date:                   Mon, March 14th 14:41:14 CET 2005
        Affected products:      9.1, 9.2
                                SUSE Linux Enterprise Server 9
                                Novell Linux Desktop 9
        Vulnerability Type:     remote command execution
        Severity (1-10):        5
        SUSE default package:   Yes.
        Cross References:       -

    Content of this advisory:
        1) security vulnerability resolved: Buffer overflows in OpenSLP.
           problem description
        2) solution/workaround
        3) special instructions and notes
        4) package location and checksums
        5) pending vulnerabilities, solutions, workarounds:
             - squirrelmail
             - Koffice
        6) standard appendix (further information)

______________________________________________________________________________

1) problem description, brief discussion

    The SUSE Security Team reviewed critical parts of the OpenSLP package,
    an open source implementation of the Service Location Protocol (SLP).
    SLP is used by Desktops to locate certain services such as printers and
    by servers to announce their services.
    During the audit, various buffer overflows and out of bounds memory access
    have been fixed which can be triggered by remote attackers by sending
    malformed SLP packets.

2) solution/workaround

    There is no easy workaround except to shut down the slpd and to stop using
    involved clients.

3) special instructions and notes

    Please make sure that all running instances of slpd which were started
    before the update are terminated.
    After the update, run the following command as root:

                   /usr/sbin/rcslpd try-restart

4) package location and checksums

    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 for installation from the maintenance web.

    x86 Platform:

    SUSE Linux 9.2:
          e183a877674fd83b401759c071f8ebfb
          b68232aa97424dea8938fb07c67ee968
          d15cb7cd7b224811cca38d4992d6dde9
    patch rpm(s):
          24fecfe10275f3995be1248307a29d8c
          0b0d8b6a0bbdc8b4962f12ee0465a083
          593b7c9104f1179761c2cac54431fec7
    source rpm(s):
          a4852023f752182d68cea815d5905d7e

    SUSE Linux 9.1:
          fa20a6d60a64aff0998eed99fab4a9af
          604d8b96c9bfbce6b2fac07e37465636
          cd6851d2adcf9439c9dcc317de052089
    patch rpm(s):
          7b4688c03fd664d6742a70245530d4a6
          4b46e36bd47cbb8ce2d08225dcca2c88
          002c614947ede188c85bb4fb62dfdbd6
    source rpm(s):
          2b29878d5706dccf0b5b5902c3e9315c



    x86-64 Platform:

    SUSE Linux 9.2:
          dba5224660ab6f76846d5be2d2c3531d
          6ab38f02002f44e24e9617794c7a50b5
          d3ccb03fe6c509b05a278c60ca7be889
    patch rpm(s):
          a9c86a43725a13fb14c86af85ace7131
          cc83600072f4d3f5ededeb60c16bc25b
          b91a5bb0ce85bd5f30db9c794618dc00
    source rpm(s):
          a4852023f752182d68cea815d5905d7e

    SUSE Linux 9.1:
          f15832a7d86cad37f73671123c3a1706
          e418cd6a08fce7a0091fef7b4f801dd2
          5f409e569a149cf83ddaf7fdb6a41dcb
    patch rpm(s):
          737bb45b6d95f0fac5d31f2b95924b1d
          8a14bb253b411bf6de617a557b2dcd6f
          6936b808204a5a48faccdf8446b72a80
    source rpm(s):
          2e443c1bedac57827cc9d2363e0d25b1

______________________________________________________________________________

5)  Pending vulnerabilities in SUSE Distributions and Workarounds:

    - squirrelmail
    New squirrelmail packages for the S/MIME plugin command injection
    vulnerability are available on our ftp servers.

    - Koffice
    New Koffice packages are available on our ftp servers, fixing
    buffer overflows in the pdf engine.

______________________________________________________________________________

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 recommend against subscribing to security lists that cause the
       e-mail 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
       file name of the rpm package that you have downloaded. Of course,
       package authenticity verification can only target an uninstalled 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  .


  - 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 .
    The  public key is listed below.
    ====================================================================