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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                cups
        Announcement-ID:        SUSE-SA:2004:031
        Date:                   Wednesday, Sep 15th, 15:30:00 MEST 2004
        Affected products:      8.1, 8.2, 9.0, 9.1
                                SUSE Linux Enterprise Server 8, 9
                                SUSE Linux Desktop 1.0
        Vulnerability Type:     remote code execution
        Severity (1-10):        6
        SUSE default package:   Yes.
        Cross References:       CAN-2004-0801
                                CAN-2004-0558

    Content of this advisory:
        1) security vulnerability resolved:
             - remote command execution and remote DoS in CUPS
           problem description
        2) solution/workaround
        3) special instructions and notes
        4) package location and checksums
        5) pending vulnerabilities, solutions, workarounds:
            - squid
            - OpenOffice
            - mozilla
            - mpg123
            - ImageMagick
        6) standard appendix (further information)

______________________________________________________________________________

1) problem description, brief discussion

   The Common Unix Printing System (CUPS) enables local and remote users to
   obtain printing functionallity via the Internet Printing Protocol (IPP).
     Alvaro Martinez Echevarria has found a remote Denial of Service condition
   within CUPS which allows remote users to make the cups server unresponsive.
     Additionally the SUSE Security Team has discovered a flaw in the
   foomatic-rip print filter which is commonly installed along with cups.
   It allows remote attackers, which are listed in the printing ACLs, to
   execute arbitrary commands as the printing user 'lp'.


2) solution/workaround

   If you use CUPS, we recommend an update in any case. Additionally the IPP
   port (TCP port 631) should be firewalled and the printing ACLs should
   be set up in a way to reflect the local security policy.


3) special instructions and notes

   After successfully updating the cups package, you need to run the following
   command as root:

     rccups restart


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.1:
          976655f117091c2bbc78399ffedf6c9c
          f4af26bd260fc756e2070c340105295d
          90cf964bf8b3ea5567754b15c0ab6988
          b67b7187ecb708d7ec2980f7cdcdaa81
    patch rpm(s):
          ce0f75db69c838557ecda3e3300bb763
          213cbdc01c0f39895f75eb6816641b82
          9c47790dcd6fa339ea7a8d21ad841e54
          8ccae3fb4988acf0c829ffe491472716
    source rpm(s):
          96a63ac94b63f0d54d16bd2d3ea73a24
          18816a89350fe3fa234506d40e4812b1

    SUSE Linux 9.0:
          f72e1b1c033695ef9f3fe9a64ace220b
          46f540ce3bcf72a870eeb2ef78d1e7ec
          9c9d4eb93c3dbf2ad740f6041224ff90
          4f5c750a1f756161407e4186b378ac51
    patch rpm(s):
          91b88efa969bb367ead02dfa686f5711
          9952d1df78213228f1a0fc129c60331a
          e83d2d6a85445fdaf186e4eba91a68da
          3d91bc3f72cfb8efa4c1a38bf6a46d60
    source rpm(s):
          236dd9aab66ee87ef73cfe9c7a4dd3a4
          56b6200d339a0bd727b102b65d327493

    SUSE Linux 8.2:
          5092cfbf2d9f71b53cfa571d23ac8e26
          1b52320ac8e50797b9e140ba0339008c
          b0cc87346a3b2270081123bbb5fd932a
    patch rpm(s):
          d67014a864afaa86952ed752d89a251a
          be6ae574c2f26a7f07d1b5e16f4ede02
          c176435d584a763ae5b57dcde996f82c
    source rpm(s):
          870f0825115fdf9526beb6e1ec867381

    SUSE Linux 8.1:
          b8a1daf19c2fa58fecc3f9dafb8c4c8d
          9f7a2dbc92804cb54749e72426d79a62
          7a82aedac6586fa27109e3576f5c4c27
    patch rpm(s):
          341ebcf57e793a836b5475353cb21e7c
          3b75cf2265150044560555785e8e4c82
          926eca878ee8c36c4efa509d7b7243d4
    source rpm(s):
          ffc7b24d6638f04933621b9b49bb9e9e



    x86-64 Platform:

    SUSE Linux 9.1:
          fc7b3c21d0bdd1b5617263045a0f0058
          4490d72429d54417049a4daabc763e56
          23e430a166baef8840b067f71b7ae96d
          cfc0d3052c29da4e9b9bccac8cb0211e
    patch rpm(s):
          4f347e2efa5151cee929889b18ddfed4
          5157c96ec037e965c39ee0139c6287cf
          ef1f955450463ee0a751ae1a4f5ceacc
          4f34ffee4f359ca09eaf481c2904796e
    source rpm(s):
          00ecd612999696c7f3a4e531c1a2198e
          33e32a64142f72a224691d64c50f9f66

    SUSE Linux 9.0:
          1b68c217134d058a5036f9a0058ddd0d
          1d48cc152e891fb3baeb2d2409830878
          a313c4956f44e230c0df9909ba0a7d25
          9b4d8b411702153be4a73222e6a12553
    patch rpm(s):
          f7bda7125579c9bda8cfd9f4e0f6f4a0
          608d96f3f6566a65e70a57fcc367f777
          a7d38ee463699f6152f8e42ee1da745d
          c83d5f8d7d41083bdad779505b777d11
    source rpm(s):
          c05016dadf2756e7e66c32c2c2b25858
          aa0436134b6b46418455e1c5235c36c0

______________________________________________________________________________

5)  Pending vulnerabilities in SUSE Distributions and Workarounds:

    - squid
    The NTLM authentication in squid suffers from a DoS vulnerability.
    New packages are currently being tested and will soon be available
    on our ftp servers.

    - OpenOffice
    OpenOffice sets the permissions of tmp-files according to the umask,
    which might be unsuitable. This will be fixed in upcoming distributions.
    If you work in an untrusted environment, you may set the $TEMP, $TMP and
    $TMPDIR environment variables to a location within your $HOME as a
    workaround.

    - mozilla
    We are in the process of releasing updates for mozilla (and related
    browsers), fixing various issues: CAN-2004-0597, CAN-2004-0718,
    CAN-2004-0722, CAN-2004-0757, CAN-2004-0758, CAN-2004-0759, CAN-2004-0760,
    CAN-2004-0761, CAN-2004-0762, CAN-2004-0763, CAN-2004-0764 and
    CAN-2004-0765.
    We will give you concrete details in a separate mozilla advisory when the
    updates are available.

    - mpg123
    A buffer overflow in the decoding of data streams has been fixed. New
    packages are available on our ftp servers. CAN-2004-0805 has been
    assigned to this issue.

    - ImageMagick
    A buffer overflow in the code handling BMP images has been fixed.
    New packages are available on our ftp servers. CAN-2004-0827 has been
    assigned to this issue.

______________________________________________________________________________

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  .


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