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

______________________________________________________________________________

                        SUSE Security Announcement

        Package:                ImageMagick
        Announcement-ID:        SUSE-SA:2005:017
        Date:                   Wed, 23 Mar 2005 14:00:00 +0000
        Affected products:      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 code execution
        Severity (1-10):        5
        SUSE default package:   no
        Cross References:       CAN-2005-0397
                                CAN-2005-0759
                                CAN-2005-0760
                                CAN-2005-0761
                                CAN-2005-0762

    Content of this advisory:
        1) security vulnerability resolved:
             several security problems in ImageMagick
           problem description
        2) solution/workaround
        3) special instructions and notes
        4) package location and checksums
        5) pending vulnerabilities, solutions, workarounds:
            See SUSE Security Summary Report.
        6) standard appendix (further information)

______________________________________________________________________________

1) problem description, brief discussion

    This update fixes several security issues in the ImageMagick program suite:
    
    - A format string vulnerability was found in the display program
      which could lead to a remote attacker being to able to execute code
      as the user running display by providing handcrafted filenames of
      images. This is tracked by the Mitre CVE ID CAN-2005-0397.

    Andrei Nigmatulin reported 4 problems in older versions of ImageMagick:
    
    - A bug was found in the way ImageMagick handles TIFF tags.
      It is possible that a TIFF image file with an invalid tag could
      cause ImageMagick to crash.
      This is tracked by the Mitre CVE ID CAN-2005-0759.

      Only ImageMagick version before version 6 are affected.

    - A bug was found in ImageMagick's TIFF decoder.
      It is possible that a specially crafted TIFF image file could
      cause ImageMagick to crash.
      This is tracked by the Mitre CVE ID CAN-2005-0760.

      Only ImageMagick version before version 6 are affected.

    - A bug was found in the way ImageMagick parses PSD files.
      It is possible that a specially crafted PSD file could cause
      ImageMagick to crash.
      This is tracked by the Mitre CVE ID CAN-2005-0761.

      Only ImageMagick version before version 6.1.8 are affected.

    - A heap overflow bug was found in ImageMagick's SGI parser.
      It is possible that an attacker could execute arbitrary code
      by tricking a user into opening a specially crafted SGI image
      file.
      This is tracked by the Mitre CVE ID CAN-2005-0762.

      Only ImageMagick version before version 6 are affected.

2) solution/workaround

    Please install the updated packages.

3) special instructions and notes

    None.

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.2:
               e0abc35e5b6e62c411d20ef6e2e9f977
               03e732ad0f84a86746b9c227fc89b445
               c284ca68e325b91406ddd7d89d469578
               1b266f8322f93bf46889bcede41807b2
    
    SUSE Linux 9.1:
               f9b715bc0b7a903d7d9ed05bb185e305
               a2f7fc378cfe423636e85d41ce2e84a3
               bd64b2c1a6725453e5c76fb8fa6504a9
               b8b09bdc13ad121251b206b0c867250a
    source rpm(s):
               25266f599e107cb3587b78311c3526d7
    
    SUSE Linux 9.0:
               efe3d14315a46951b3c9b67d77ae7e24
               d2edc9ca9c44981a804081ceee7995e8
               c596c37ffc1037edd206f2ed2b7aba8c
               0cdf7ec0f6a284fd1ecd0f8b4669f106
    source rpm(s):
               388fc41c453baecab3249d0c5520e509
    
    SUSE Linux 8.2:
               f1fd06f68f5d1340aa48a1249a666b42
               476eb03a384a7f3295f0933bfd22037b
               1fe5babe00b1a2e3b29b27afdc49a5eb
               7b4954080bed5957fc4dafc139877ffb
    source rpm(s):
               fb728261f74de1c886b8e89c6ccdc527
    
    x86-64 Platform:
    
    SUSE Linux 9.2:
               2b5031672b87983839255c62a8d2b6c6
               65e2f75380c5c09318de2c2d5341dd8f
               dd81443b6ddd154a7c0f5af0ba107686
               a7900a8703a0fe17ff64ff9dcb9e52f4
    source rpm(s):
               610adb7f10d61555aa46b27e29eebf05
    
    SUSE Linux 9.1:
               6ea3b05343ea37f54b0912576e5bc6e7
               7b9e5c6e6094abc2f11f2817ca513b89
               c0f61d39f21a1b365f301515230a357b
               c9e54772c1cd1ad6a06bafd926377095
    source rpm(s):
               49128ab7a073c5c65883801bafa60a6b
    
    SUSE Linux 9.0:
               7b7cbce2c54582984747576efe1d551d
               108267eb5c839b17b878d63a351c1ee1
               34a4699f690dc4b11c347274abddb6fe
               83d2c15b6ba09df08b560d131de2cf5b
    source rpm(s):
               a5c25371a0c311c715dd331309649a57


______________________________________________________________________________

5)  Pending vulnerabilities in SUSE Distributions and Workarounds:

    See SUSE Security Summary Report.

______________________________________________________________________________

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 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 .
@suse.de>.
    The  public key is listed below.
    ====================================================================