PGP SIGNED MESSAGE
Hash: SHA1
SUSE Security Announcement
Package: ImageMagick
Announcement ID: SUSE-SA:2006:050
Date: Fri, 08 Sep 2006 17: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 9.2
SuSE Linux Desktop 1.0
SuSE Linux Server 4
SuSE Linux School Server
SuSE Linux Standard Server 8
SUSE SLED 10
Vulnerability Type: code execution
Severity (1-10): 5
SUSE Default Package: no
Cross-References: CVE-2006-3743, CVE-2006-3744, CVE-2006-4144
Content of This Advisory:
1) Security Vulnerability Resolved:
ImageMagick various 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
Several security problems have been fixed in ImageMagick:
- CVE-2006-3744: Several heap buffer overflows were found in the Sun
Bitmap decoder of ImageMagick during an audit by the Google Security
Team. This problem could be exploited by an attacker to execute code.
- CVE-2006-3743: Multiple buffer overflows were found by the Google
Security team in the XCF handling due to incorrect bounds checking.
This problem could be exploited by an attacker to execute code.
- CVE-2006-4144: An integer overflow in the ReadSGIImage function can
be used by attackers to potentially execute code.
- An infinite loop in ImageMagick caused by TransformHSB was fixed.
- An infinite loop in the handling of TIFF images was fixed.
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
None.
4) Package Location and Checksums
The preferred method for installing security updates is to use the YaST
Update (YU) tool. YU 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 <file.rpm>
to apply the update, replacing <file.rpmwith the filename of the
downloaded RPM package.
x86 Platform:
SUSE LINUX 10.1:
SUSE LINUX 10.0:
SUSE LINUX 9.3:
SUSE LINUX 9.2:
Power PC Platform:
SUSE LINUX 10.1:
SUSE LINUX 10.0:
x86-64 Platform:
SUSE LINUX 10.1:
SUSE LINUX 10.0:
SUSE LINUX 9.3:
SUSE LINUX 9.2:
Sources:
SUSE LINUX 10.1:
SUSE LINUX 10.0:
SUSE LINUX 9.3:
SUSE LINUX 9.2:
maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
SuSE Linux Server 4
SLES SDK 9
Novell Linux Desktop 9
SuSE Linux Standard Server 8
SuSE Linux School Server
SuSE Linux Desktop 1.0
SLE SDK 10
SUSE SLED 10
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 <file>
replacing <filewith the name of the file where you saved the
announcement. The output for a valid signature looks like:
gpg: Signature made <DATEusing RSA key ID 3D25D3D9
gpg: Good signature from "SuSE Security Team <security (AT) suse (DOT) de>"
where <DATEis 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
- 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 <file.rpm>
to verify the signature of the package, replacing <file.rpmwith the
filename of the RPM package downloaded. The package is unmodified if it
contains a valid signature from build (AT) suse (DOT) 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 <filename.rpm>
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 (AT) suse (DOT) 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 (AT) suse (DOT) 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-subscribe (AT) suse (DOT) com>.
suse-security-announce (AT) suse (DOT) com
- SUSE's announce-only mailing list.
SUSE's security announcements are sent to this list.
To subscribe, send an e-mail to
<@suse.com>.
For general information or the frequently asked questions (FAQ),
send mail to <suse-security-info (AT) suse (DOT) comor
<suse-security-faq (AT) suse (DOT) com>.
SUSE's security contact is <security (AT) suse (DOT) comor <security (AT) suse (DOT) de>.
The <security (AT) suse (DOT) depublic 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, the
clear text signature should show proof of the authenticity of the text.
SUSE Linux Products GmbH provides 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 (AT) suse (DOT) de>
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build (AT) suse (DOT) de>
- PGP PUBLIC KEY BLCK
Version: GnuPG v1.4.2 (GNU/Linux)
+
=ypVs
- PGP PUBLIC KEY BLCK
PGP SIGNATURE
Version: GnuPG v1.4.2 (GNU/Linux)
=Njb8
PGP SIGNATURE