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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                libtiff
        Announcement-ID:        SUSE-SA:2004:038
        Date:                   Friday, Oct 22nd 2004 18:00 MEST
        Affected products:      8.1, 8.2, 9.0, 9.1
                                SUSE Linux Enterprise Server 8, 9
                                SUSE Linux Desktop 1.0
        Vulnerability Type:     local privilege escalation
        Severity (1-10):        9
        SUSE default package:   yes
        Cross References:       CAN-2004-0803
                                CAN-2004-0804
                                CAN-2004-0886
                                CAN-2004-0929

    Content of this advisory:
        1) security vulnerability resolved:
             - several buffer overflows and related problems in
               libtiff were fixed.
           problem description
        2) solution/workaround
        3) special instructions and notes
        4) package location and checksums
        5) pending vulnerabilities, solutions, workarounds:
            - security problems in PDF viewers	    - freeradius denial of service problems
	    - mpg123 buffer overflow
        6) standard appendix (further information)

______________________________________________________________________________

1) problem description, brief discussion

   libtiff is used by image viewers and web browser to view "TIFF" images.
   These usually open and display those images without querying the user,
   making a normal system by default vulnerable to exploits of image
   library bugs.

   Chris Evans found several security related problems during an audit of
   the image handling library libtiff, some related to buffer overflows,
   some related to integer overflows and similar. This issue is being
   tracked by the CVE ID CAN-2004-0803.

   Matthias Claasen found a division by zero in libtiff. This is tracked
   by the CVE ID CAN-2004-0804.

   Further auditing by Dmitry Levin exposed several additional integer
   overflows. These are tracked by the CVE ID CAN-2004-0886.

   Additionally, iDEFENSE Security located a buffer overflow in the OJPEG
   (old JPEG) handling in the SUSE libtiff package. This was fixed by
   disabling the old JPEG support and is tracked by the CVE ID CAN-2004-0929.

   SUSE wishes to thank all the reporters, auditors, and programmers   for helping to fix these problems.

2) solution/workaround

   There is no workaround. Update the libtiff packages.

3) special instructions and notes

   Make sure that you restart your web browser after updating.

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.

    You can also use the YaST Online Update tool to install the security
    updates.

    Our maintenance customers are being notified individually. The packages
    are being offered for installation from the maintenance web.

    x86 Platform:

    SUSE Linux 9.1:
          cd373c181599ebbf3be0f021b811c7da
    patch rpm(s):
          a45416ea1ac9628b9e4e7e6f09653cb5
    source rpm(s):
          2387abe21eebb97f319b6ddf1a982314

    SUSE Linux 9.0:
          db8b4d23eb887b3c391f5262f766ff86
    patch rpm(s):
          58112fc9e5c6395bc316f3b46ffeb0ca
    source rpm(s):
          0810ea6ffe77b7a450698386a6238e61

    SUSE Linux 8.2:
          339e0ce21cceadb883d2022ec01c1219
    patch rpm(s):
          608c1b39e6d67c9da02e02d2176b7a97
    source rpm(s):
          8891d3c8ff0dd0f283f63d4b3021b894

    SUSE Linux 8.1:
          
______________________________________________________________________________

5)  Pending vulnerabilities in SUSE Distributions and Workarounds:

    - security problems in pdf viewers        Chris Evans, Dmitry Levin and others found several buffer and
        integer overflow problems in xpdf and xpdf clones.
        These are being tracked under the CVE Ids CAN-2004-0888 and
        CAN-2004-0889.
        New packages will be available soon.

    - freeradius
        Several bugs that can be abused to remotely crash freeradius have
        been discovered (CAN-2004-0938, CAN-2004-0960, CAN-2004-0961).
        New packages will be available soon.

    - mpg123 
        A buffer overflow in mpg123 has been discovered. New packages will
        be available soon.

______________________________________________________________________________

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