-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: ImageMagick
Announcement ID: SUSE-SA:2006:066
Date: Tue, 14 Nov 2006 12:00:00 +0000
Affected Products: Novell Linux Desktop 9
SLE SDK 10
SLES SDK 9
SUSE LINUX 10.1
SUSE LINUX 10.0
SUSE LINUX 9.3
SuSE Linux Desktop 1.0
SuSE Linux Openexchange Server 4
SuSE Linux School Server
SuSE Linux Standard Server 8
SUSE SLED 10
Vulnerability Type: remote denial of service
Severity (1-10): 5
SUSE Default Package: no
Cross-References: CVE-2006-5456
Content of This Advisory:
1) Security Vulnerability Resolved:
ImageMagick security problems
Problem Description
2) Solution or Work-Around
3) Special Instructions and Notes
4) Package Location and Checksums
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
See SUSE Security Summary Report.
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
Two security problems were found in the GraphicsMagick tool set which
are also present in ImageMagick.
CVE-2006-5456: Multiple buffer overflows in ImageMagick allowed
user-assisted attackers to cause a denial of service and possibly
execute execute arbitrary code via (1) a DCM image that is not
properly handled by the ReadDCMImage function in coders/dcm.c, or
(2) a PALM image that is not properly handled by the ReadPALMImage
function in coders/palm.c.
Additionally a segfault regression when converting a PGM image was
fixed on SLE 10.
2) Solution or Work-Around
Please install the updated packages.
3) Special Instructions and Notes
None.
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:
SUSE LINUX 10.1:
53a00589ee258f1e45a692e9ce12aeba
c30d0dfeee41c23b99d833358b274f55
a0d70475369c851b8a7a36995ae38f89
bdb09dd70f7883d63a40f30680eca4cd
5aa843a0c9b21be524034977dc7f5762
SUSE LINUX 10.0:
cd473f0b81b40c2d7387eeccec9126a6
29caed1aaa2aad1cb02a6dc3043e797b
b4b4c654d7f1315e5ff2f524da2831f1
e02ff46acf16bfa5d7a8abdda4f9c10b
abd013195ae2e6dd6f3d36f1a40faf9d
SUSE LINUX 9.3:
a6015f397a33caca9465325d3593e408
4ecdae14291bfac5ac0fb2030a33cae5
6073ce67170c759aafb362879a78d3ce
ba2e72511d4cf8bc43883fc965d176af
f18b1fd1d40e323d0656943b7aacbf7a
Power PC Platform:
SUSE LINUX 10.1:
0ce17968ee4b88e82b03969d83cfb877
6dd51385fd0a7fa296ce28559bbed9c3
952219aef97fd57e91fb1dfc5c67eeba
61b69423fef382664812b67bd7e467a5
017968d9d41f1618b33eedd76fc48c10
SUSE LINUX 10.0:
327ca2796926ffef811188996a666bdd
1c1fe905aa0c0b944eae02bb6188ac24
6941f64579f8e2ea751a9f61ac731b60
6de9945e06b2332f4c7f8e59623703b5
0bc9c802c61e8004f554eec60983cc07
x86-64 Platform:
SUSE LINUX 10.1:
3b0fc7e0d61599bb6ec8de677de12069
a8d269a5e6d216919d4f3ef5048c07f0
39756fc165eb7dcf416a4120ac52818a
66f2643a53e78307f5d9081b475fe53b
b4f8088f97b2735f42e52c46b801ab83
SUSE LINUX 10.0:
aabb1f9abb5bf686b7f872cc23d891d0
52d9ab106555003e8fa3a72f1d5c3cb4
aac46f4da8928ef27556a1a971b0580f
00a81102fa19303cbf40c0414e361b6f
a8114375ac411502b5a4b367c587125a
SUSE LINUX 9.3:
ad2633bb68a390e8bcb1cf248ba95020
dd507ecf6222ed14ce3f90d51a6d996e
7a403f2364da96b132c7957f80c6d540
4b0a5865abec3dae751ba1b5ae653044
74cd0a2dad875a8019adf12a2536743a
Sources:
SUSE LINUX 10.1:
78474b3af1b7e120694e2e3cc6d034f4
SUSE LINUX 10.0:
0ae17c894f34961cfb3f0e070167c8f0
SUSE LINUX 9.3:
f2a276ad3c03ab1ffd7e10336e70274c
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
SuSE Linux Openexchange Server 4
http://support.novell.com/techcenter/psdb/54784cdc395efc4acd3491b3f202e583.html
SLES SDK 9
http://support.novell.com/techcenter/psdb/54784cdc395efc4acd3491b3f202e583.html
Novell Linux Desktop 9
http://support.novell.com/techcenter/psdb/54784cdc395efc4acd3491b3f202e583.html
SuSE Linux Standard Server 8
http://support.novell.com/techcenter/psdb/54784cdc395efc4acd3491b3f202e583.html
SuSE Linux School Server
http://support.novell.com/techcenter/psdb/54784cdc395efc4acd3491b3f202e583.html
SuSE Linux Desktop 1.0
http://support.novell.com/techcenter/psdb/54784cdc395efc4acd3491b3f202e583.html
SLE SDK 10
http://support.novell.com/techcenter/psdb/54784cdc395efc4acd3491b3f202e583.html
SUSE SLED 10
http://support.novell.com/techcenter/psdb/54784cdc395efc4acd3491b3f202e583.html
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
See SUSE Security 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:
suse-security@suse.com
- General Linux and SUSE security discussion.
All SUSE security announcements are sent to this list.
To subscribe, send an e-mail 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 e-mail to
.
For general information or the frequently asked questions (FAQ),
send mail to or
.
==================================================================== SUSE's security contact is or .
The public key is listed below.
====================================================================
