______________________________________________________________________________

                        SuSE Security Announcement

        Package:                cups
        Announcement-ID:        SuSE-SA:2003:002
        Date:                   Thursday, Jan 2nd 2003 09:30 MEST
        Affected products:      7.1, 7.2, 7.3, 8.0, 8.1
                                SuSE Linux Enterprise Server 8
                                UnitedLinux 1.0
        Vulnerability Type:     local and remote privilege escalation
        Severity (1-10):        7
        SuSE default package:   since 8.1: yes
                                prior 8.1: no
        Cross References:       CAN-2002-1366
                                CAN-2002-1367
                                CAN-2002-1368
                                CAN-2002-1369
                                CAN-2002-1371
                                CAN-2002-1372
                                CAN-2002-1383
                                CAN-2002-1384


    Content of this advisory:
        1) security vulnerability resolved: several bugs
           problem description, discussion, solution and upgrade information
        2) pending vulnerabilities, solutions, workarounds:
             - none
        3) standard appendix (further information)

______________________________________________________________________________

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

    CUPS is a well known and widely used printing system for unix-like
    systems. iDFENSE reported several security issues with CUPS that can
    lead to local and remote root compromise. The following list
    includes all vulnerabilities:
      - integer overflow in HTTP interface to gain remote
        access with CUPS privileges
      - local file race condition to gain root (bug mentioned
        above has to be exploited first)
      - remotely add printers      - remote denial-of-service attack due to negative length in
        memcpy() call
      - integer overflow in image handling code to gain higher privileges
      - gain local root due to buffer overflow of 'options' buffer
      - design problem to gain local root (needs added printer, see above)
      - wrong handling of zero width images can be abused to gain higher
        privileges
      - file descriptor leak and denial-of-service due to missing checks
        of return values of file/socket operations

    Since SuSE 8.1 CUPS is the default printing system.

    As a temporary workaround CUPS can be disabled and an alternative
    printing system like LPRng can be installed instead.

    New CUPS packages are available on our FTP servers. Please, install
    them to fix your system.

    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.



    Intel i386 Platform:

    SuSE-8.1:
      
      2531f8cf2c7ffbc45f5bdabbad31b312
    patch rpm(s):
      
      048c97ac172f3a838bb3e4789250cd56

      
      3daffc6cac8a067c2a8b52768ada25a0
    patch rpm(s):
      
      74045133ea1780aa311dab78af0ea7a5

      
      593fedd856a9568147f76e70cdd32b94
    patch rpm(s):
      
      9a67ef7fd0162283d662581866a68263

    source rpm(s):
      
      cad9236a0f71d1ad263c4c79e6d4337f

    SuSE-8.0:
      
      9d1d9c3cc395e6355da6f8f1b9ccee5c
    patch rpm(s):
      
      b17bfb78daac61a05c92e938e2d89463
    
      
      9ec263cb51c223798818509f50246ec9
    patch rpm(s):
      
      a59edfa5ba38116ccd4c264863c4bbf8
    
      
      fef9316839a2747111201b5e035295ad
    patch rpm(s):
      
      80525203e712a959badab348d07f81a9
    
    source rpm(s):
      
      4cad7db5ae424516502c820d29402989

    SuSE-7.3:
      
      e456c6027c8e63a8e3c1773cc2d4d531
    
      
      53bfc694bc74e4220eba66f569dd837b
    
      
      7ed2406d49693fa148eaf27ac3083010
    
    source rpm(s):
      
      0e33f13aedce730069b3e1788eb19a0e

    SuSE-7.2:
      
      f6651e3f296ac2e19edb6403c2f92e7e
    source rpm(s):
      
      42015fbabce4f6bc22cf4d94061ca657

    SuSE-7.1:
      
      f9b1f8aee6cad0ef7787dffc2a4309b1
    source rpm(s):
      
      f1db871d4a9b921bdffe71023fb294f9



    Sparc Platform:

    SuSE-7.3:
      
      0c614102570716b33a96723867d071df
    
      
      d15e6354a448240275966dd46f7e02ed
    
      
      b21ce5aaa79dd60897eed762e119a65d
    
    source rpm(s):
      
      83bd4b66daeba343549d0f8abd80a537



    AXP Alpha Platform:

    SuSE-7.1:
      
      f68f6f596934365ae44d8dafc7aaa897
    source rpm(s):
      
      f10402e4bada55969e6a1fb651c8f37b



    PPC Power PC Platform:

    SuSE-7.3:
      
      3b15601c7838620311514cc244e45078
    
      
      c1ca0adfa7c4091260c64e3c58ea20f1
    
      
      b63eef9ec012b5e17bfcfce558829f94

    source rpm(s):
      
      58850c0f45f62a79146fa536fc91ded7

    SuSE-7.1:
      
      1a31de608674e8a1224b22bd3b9a792a
    source rpm(s):
      


______________________________________________________________________________

2)  Pending vulnerabilities in SuSE Distributions and Workarounds:

    - none
______________________________________________________________________________

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 
       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-subscribe@suse.com>.

    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
                <suse-security-announce-subscribe@suse.com>.

    For general information or the frequently asked questions (faq) 
    send mail to:
        <suse-security-info@suse.com> or
        <suse-security-faq@suse.com> respectively.

    ====================================================================    SuSE's security contact is <security@suse.com> or <security@suse.de>.
    The <security@suse.de> 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 <security@suse.de>
pub  1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@suse.de>