-----BEGIN PGP SIGNED MESSAGE-----
______________________________________________________________________________
SUSE Security Announcement
Package: freetype2, freetype2-devel
Announcement ID: SUSE-SA:2006:037
Date: Tue, 27 Jun 2006 12:00:00 +0000
Affected Products: SUSE LINUX 10.1
SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE LINUX 9.2
SUSE SLES 9
Vulnerability Type: remote code execution
Severity (1-10): 8
SUSE Default Package: yes
Cross-References: CVE-2006-0747
CVE-2006-1861
CVE-2006-2661
Content of This Advisory:
1) Security Vulnerability Resolved:
several integer overflows
Problem Description
2) Solution or Work-Around
3) Special Instructions and Notes
4) Package Location and Checksums
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
none
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
The freetype2 library renders TrueType fonts for open source projects.
More than 900 packages on SUSE Linux use this library. Therefore the
integer overflows in this code found by Josh Bressers and Chris Evans
might have a high impact on the security of a desktop system.
The bugs can lead to a remote denial-of-service attack and may lead to
remote command execution. The user needs to use a program that uses
freetype2 (almost all GUI applications do) and let this program process
malicious font data.
2) Solution or Work-Around
No work-around known.
3) Special Instructions and Notes
Please log out from your window-manager session and log in again
to let all applications restart and load the new code.
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:
d8159af0dd876c9f75a30c7027ccc65e
14ed91a58dbbf592bad515a34fa46bf1
SUSE LINUX 10.0:
e55d8a3eb8a0e203db16703d4eb24ffa
5f8bad1411007aab9d190036cadc0d1b
SUSE LINUX 9.3:
76edb89bf583274c0cdc13a4a60a1a33
5995bb6179b03f75c174355c7303e4ef
SUSE LINUX 9.2:
62b0c3c6886439cf10b4f64d0930f251
0df43df0ac31ecb637acda13a1c558bb
Power PC Platform:
SUSE LINUX 10.1:
1316c1937957047ca3293a4181d1d16e
fb738052648a6fddf2e6e791e06c4b9b
SUSE LINUX 10.0:
5a1d2fa14ba666893e0e61ebbc583f9e
4c92c8bc862aaf734974da7ae0a8e8d2
x86-64 Platform:
SUSE LINUX 10.1:
b8c72431885e3b302954c83bbd3615f8
c957ce5e918d0ee7933db8c859362eb2
da300d9b65f6ec99b59045a4ff17b848
7f746c754434d96c6e1d1b1a4f42719f
SUSE LINUX 10.0:
ec8a92f9958022f27ded53222e6d16cb
b71540b7a43d88060a15f46a282083a2
59ef42def49b6b8d57fc4927bbe3e503
7749224202098d4cec74b15621a6bf90
SUSE LINUX 9.3:
fe14dad1164731b5abc35e54bea51753
916649bdc38f5c7d2f20b7f9c306928d
5292d176535b6bc68dfa64a9087e783c
1c9e160e832a33be4233653ead4745e6
SUSE LINUX 9.2:
0df14e0676312be2bb28b0c1beb2245c
95fd288ab5afc988c6881b2a6f8a9c03
8a56ae60affaa2ad3913126bb45684e2
74fa3c308c0d2541fe71ba8c1d57e0e3
Sources:
SUSE LINUX 10.1:
3d5053bd231a06234daf2b30c93b8aae
SUSE LINUX 10.0:
b7deaf1486d41b3f7462adb8c2c6a282
SUSE LINUX 9.3:
12dc71a010ddb89f753429892e46065e
SUSE LINUX 9.2:
1beda05b38c0445cb82bed8f01b3a62a
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
none
______________________________________________________________________________
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.
====================================================================
