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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                cups
        Announcement ID:        SUSE-SA:2008:012
        Date:                   Thu, 06 Mar 2008 11:00:00 +0000
        Affected Products:      SUSE LINUX 10.1
                                openSUSE 10.2
                                openSUSE 10.3
                                SuSE Linux Enterprise Server 8
                                SUSE SLES 9
                                Novell Linux Desktop 9
                                Open Enterprise Server
                                Novell Linux POS 9
                                SUSE Linux Enterprise Desktop 10 SP1
                                SUSE Linux Enterprise Server 10 SP1
        Vulnerability Type:     remote code execution
        Severity (1-10):        7
        SUSE Default Package:   yes
        Cross-References:       CVE-2008-0596
                                CVE-2008-0597
                                CVE-2008-0882

    Content of This Advisory:
        1) Security Vulnerability Resolved:
             remote code execution and multiple denial-of-service bugs
           Problem Description
        2) Solution or Work-Around
        3) Special Instructions and Notes
        4) Package Location and Checksums
        5) Pending Vulnerabilities, Solutions, and Work-Arounds:
            none
        6) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Problem Description and Brief Discussion

   CUPS is the default printer system on SUSE Linux.

   The current security update of cups fixes a double-free bug in the function
   process_browse_data() that can lead to a remote denial-of-service by crash-
   ing cupsd or possibly to a remote code execution (CVE-2008-0882).
   The bug can only be exploited if cupsd listens to 631/udp by crafted UDP
   Browse packets.
   Additionally two remote denial-of-service bugs were fixed. The first one
   can be triggered via crafted IPP packets to use a pointer after it was
   freed (CVE-2008-0597) and the second issue is a memory-leak caused by a
   large number of requests to add and remove shared printers (CVE-2008-0596).

2) Solution or Work-Around

   No work-around known. Please install the new cups package.

3) Special Instructions and Notes

   Restart the cups server 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:
   
   openSUSE 10.3:
             58a5a276cce67effbd6fbe8154bbfb61
             6d40b6ce8b5fd0a72cd25d8f6fbf8859
             9b3055b00b3ca8ff417b72a981b9e301
             8f8e73fe3aece7a53f4f51bfce87d921
   
   openSUSE 10.2:
             ce2f6be0cf30e3b71b646e62a029cb79
             0a23fa9760a2a88cd1e8451b8d5b48a6
             b87ce06a93ee2ef1062153b2a8689749
             7fc972995c533e45ce7577545576e1b9
   
   SUSE LINUX 10.1:
             4ef1069e44543a4e07048b21128c19a3
             a0ed40efdfa03596535ff90d990409cb
             f205135dea30ff1079e342e86ac0c240
             3e82329efd71ea8987c6f5ad06f1dcc3
   
   Power PC Platform:
   
   openSUSE 10.3:
             1de1c175ed2609c7b6fb17adf619a3bd
             e9b59c6c02679bf8ef010fdc9133211e
             c82e8802db9f891d8d0b8ee4ca6f1b0c
             46fd5eddc31037acd8a26bcb11d351d4
   
   openSUSE 10.2:
             3d688a3ec198f3c9a31951caf95ddbb6
             e50f0eca33d3666c938648fafd472e1b
             cffbbe682c5970e95a42af1c2a5321d5
             aef41b836d4b0f71daa623ae0fead618
   
   SUSE LINUX 10.1:
             9878a85c10c4c1299a6f6e8d7887d701
             074944cc0244f49ea5ca0c39866e5e85
             aed89c7c4d0832c7df289cf28b73cfe9
             6fb7c82e682182e4e584ede96c87f2de
   
   x86-64 Platform:
   
   openSUSE 10.3:
             fd8d905a8129fdcf79f17b6c35a1e99c
             eb74b82bc67cd0bf048ac75d56e86c54
             30a69685925386b6fd6a287463f5c596
             c47e7346ffa3054b9e79b06f4a68f4da
             15784eb2174e331113e3fd7f313fcf38
   
   openSUSE 10.2:
             3ed2e2dbb567a458071bf2f15e36fcab
             746c10e52f6e34b004906dcb705b4d3f
             becb337fcdc4e04325d8abe940056751
             2eeec7af8a643fa95bdf38f9e00b67fa
             1f7552edbbc1c7d06c7c68924f3bce8d
   
   SUSE LINUX 10.1:
             e987389ac8c86b42e35c8ec7937b837d
             a8daa44c9179ab1fd4fbeee199861658
             ce844e64c5340593a9da6828afe279b9
             e5548c55b068f015d7e18f5e02e7ce2e
             5d2a7df4d6c7c38f2fd0be0860fcee70
   
   Sources:
   
   openSUSE 10.3:
             c8beb8c8be3b611388b81bd3e7c3d9b0
   
   openSUSE 10.2:
             6a7c78bf03906366efc3c7b996db0382
   
   SUSE LINUX 10.1:
             6fadf975197cd21eb83174d32ee192c7
   
   Our maintenance customers are notified individually. The packages are
   offered for installation from the maintenance web:
   
   Open Enterprise Server
     http://support.novell.com/techcenter/psdb/1addc7e3aa69e266f0fba3fdfef8b6c7.html
   
   Novell Linux POS 9
     http://support.novell.com/techcenter/psdb/1addc7e3aa69e266f0fba3fdfef8b6c7.html
   
   Novell Linux Desktop 9
     http://support.novell.com/techcenter/psdb/1addc7e3aa69e266f0fba3fdfef8b6c7.html
   
   SuSE Linux Enterprise Server 8
     http://support.novell.com/techcenter/psdb/1addc7e3aa69e266f0fba3fdfef8b6c7.html
   
   SUSE Linux Enterprise Server 10 SP1
     http://support.novell.com/techcenter/psdb/1addc7e3aa69e266f0fba3fdfef8b6c7.html
   
   SUSE Linux Enterprise Desktop 10 SP1
     http://support.novell.com/techcenter/psdb/1addc7e3aa69e266f0fba3fdfef8b6c7.html
   
   SUSE SLES 9
     http://support.novell.com/techcenter/psdb/1addc7e3aa69e266f0fba3fdfef8b6c7.html

______________________________________________________________________________

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

   Please consult our weekly 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:

    opensuse-security@opensuse.org
        -   General Linux and SUSE security discussion.
            All SUSE security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    opensuse-security-announce@opensuse.org
        -   SUSE's announce-only mailing list.
            Only SUSE's security announcements are sent to this list.
            To subscribe, send an e-mail to
                .

    ====================================================================    SUSE's security contact is  or .
    The  public key is listed below.
    ====================================================================