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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                libtiff/tiff
        Announcement-ID:        SUSE-SA:2005:001
        Date:                   Monday, Jan 10th 2005 11:30 MET
        Affected products:      8.1, 8.2, 9.0, 9.1, 9.2
                                SUSE Linux Desktop 1.0
                                SUSE Linux Enterprise Server 8, 9
                                Novell Linux Desktop 9
        Vulnerability Type:     remote system compromise
        Severity (1-10):        8
        SUSE default package:   yes
        Cross References:       CAN-2004-1183
                                CAN-2004-1308

    Content of this advisory:
        1) security vulnerability resolved:
             - integer overflow
             - buffer overflow
           problem description
        2) solution/workaround
        3) special instructions and notes
        4) package location and checksums
        5) pending vulnerabilities, solutions, workarounds:
        6) standard appendix (further information)

______________________________________________________________________________

1) problem description, brief discussion

    Libtiff supports reading, writing, and manipulating of TIFF image files.
    iDEFENSE reported an integer overflow in libtiff that can be exploited by
    specific TIFF images to trigger a heap-based buffer overflow afterwards.

    This bug can be used by external attackers to execute arbitrary code
    over the network by placing special image files on web-pages and
    alike.
    
    Additionally a buffer overflow in tiffdump was fixed.
    
    
2) solution/workaround

    There is no workaround known.
    
    
3) special instructions and notes

    It is needed that all processes using libtiff are restarted.
    If you use GUI applications please close your X/GDM/KDM session(s) and
    log in again.
    
    
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:
          8d0c9a4295719b7b659d33b311932cce
          bbdfe23b8390265f62c5e800551eca7d
          79d0b122103b619b795872ed70a7feaa
    patch rpm(s):
          dd18c32e661a59dfda88e5318ecfb825
          a161f078c72920fde4f95f0f229e07fb
          b66e77ac565b375555f9b980145a9442
    source rpm(s):
          953f00dd4f98223d270db6e2c662e370

    SUSE Linux 9.1:
          bc883989e3deeecbc0dfb47a9daa23ff
          46a598e4914836b7e4e90094625e1587
    patch rpm(s):
          ec8d13d5b0bb4bedb2796db800ec8821
          8bfef59cd1946f889f9eb3b8f441e61a
    source rpm(s):
          59218891e1c096ee376aec6906dbbc1c

    SUSE Linux 9.0:
          339b3bbc318cc6298e07a65e82a1e07d
          6fe1432237f589dc73e348e1cdbc9068
    patch rpm(s):
          867a5a98a2ac68071be51a2426992bd9
          a185bec3b9a4a79590561d2bd7d19243
    source rpm(s):
          a4857a276db37e3a6d4fc6df2bebd230

    SUSE Linux 8.2:
          aab8d95cf757c5520830e0bed74e2d5f
          5ded8ffdd7633ce5a68a231d637f6247
    patch rpm(s):
          566e39a22033284c1266c52eac7320d3
          40521831ae56bdabde85ee92473697c5
    source rpm(s):
          f407a1cfca26d9618d19848b087983ee

    SUSE Linux 8.1:
          36ec66df028b5d24f8373282a32f1440
          7e5b60fd51d14eac8312474f2d43cda0
    patch rpm(s):
          41959759027005e272103b07054c6e26
          0ae11b9367fe84085aacd6ed1b586bff
    source rpm(s):
          b9d1ac1c51f9f935ca78628d8d2adc3e



    x86-64 Platform:

    SUSE Linux 9.2:
          d22303573664d8ef0170c1da81a65232
          d22303573664d8ef0170c1da81a65232
          27a98a68b4bda3096f6263998c41d29d
          d9f2938c822fa2131a3b2a1c4b471376
    patch rpm(s):
          f52f8c1a562151373ee98c14e22a6107
          f52f8c1a562151373ee98c14e22a6107
          cb8f1590ecc0b7ef89eeca271ab7a5c7
          e49a2d960381dea99758b7c8d34df07f
    source rpm(s):
          953f00dd4f98223d270db6e2c662e370

    SUSE Linux 9.1:
          01f564b510e02b71ed23146358b6488a
          b9fbc56e9f2250ec222c87f8a3805252
    patch rpm(s):
          813bcb747d11c80ddc30c9de98dbd344
          2a6c5c2923d9709904cdef560c996fb9
    source rpm(s):
          506ec05d53f1bc266263aa76086d8af9

    SUSE Linux 9.0:
          29e8cfa5fd6725ea02d66e43a2abeafb
          b5bccb1560f75b5fd9dd827bdc2f6424
    patch rpm(s):
          e64cdac3e6a86404d17807e12c4f7098
          9e5eb1bfc586805c8e1f65002b82234c
    source rpm(s):
          b406b3a976b892afb572be9907ab2df0

      
______________________________________________________________________________

5) pending vulnerabilities in SUSE Distributions and Workarounds:

    Please read our next summary report for more information.

______________________________________________________________________________

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 ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de .


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