-----BEGIN PGP SIGNED MESSAGE-----
______________________________________________________________________________
SUSE Security Announcement
Package: freetype2
Announcement ID: SUSE-SA:2006:045
Date: Tue, 01 Aug 2006 18:00:00 +0000
Affected Products: SLE SDK 10
SUSE LINUX 10.1
SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE LINUX 9.2
SuSE Linux Desktop 1.0
SuSE Linux Enterprise Server 8
SUSE SLES 10
SUSE SLES 9
UnitedLinux 1.0
Vulnerability Type: possible code execution
Severity (1-10): 8
SUSE Default Package: yes
Cross-References: CVE-2006-3467
Content of This Advisory:
1) Security Vulnerability Resolved:
integer overflow
Problem Description
2) Solution or Work-Around
3) Special Instructions and Notes
4) Package Location and Checksums
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
This security update fixes crashes in the PCF handling of freetype2
which might be used to crash freetype2 using applications or even
to execude code in them.
2) Solution or Work-Around
No work-around known.
3) Special Instructions and Notes
Please restart all applications using libtiff. Desktop users should logout
and re-login.
On server systems you have to restart all server applications manually.
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:
5b3f167cce62870117a4e2fa009bae4f
e927b989339e9f9bec00d1b9dcaf9a19
SUSE LINUX 10.0:
531f4629f8dc5a2875f9e1c9aec0b1b5
42dd4c6ca44ba52786519f59c83624b9
SUSE LINUX 9.3:
c4c0764be947a478d0b5583e50510903
3519d6e62b3d582bc47e5af1a2c774c6
SUSE LINUX 9.2:
146856628a74cb15457e11aa7337c31f
c416e6195fb1aa805e288526d54381af
Power PC Platform:
SUSE LINUX 10.1:
2fb95c4f2d717cf3813db084be206a9f
e42b9fb058f7fc177a5923b76d43aa1d
SUSE LINUX 10.0:
57edbb76b03b7ea2c4a0649549f2556f
3e84a91d83f2723e4f1e9174bc744976
x86-64 Platform:
SUSE LINUX 10.1:
b6e4eb912ae20cc5e2108918aa4223ce
200e0497a3aba6400b95def9fd370743
0069a1143bda97ed5c65e37561b634a6
eadbd8ec95d26e0b377c41b0a4b81ce7
SUSE LINUX 10.0:
502ee9101176c8cabe74ffa96b9c86bf
b3839f54586cb9250067b43e9c37ff4f
db9965909415db561e09bee9f6fbb445
e84c092650ccd5dee76edaa90cbb26b0
SUSE LINUX 9.3:
eef00de5d1a91266ed07285f4da34af2
c906a892e78ffd90fcd96aba1d20f0f2
62c7a3e6baab5ea1276f4e1b6bc2ca69
e5d5670a23d190565c0c3691bcf6dba7
SUSE LINUX 9.2:
de7b9ea0e3aeae01c5fac30cc34a4e55
d2abe911c1b5147c1ac917c3f2704397
b5b7030ca22d70fad00bd1ed437906bb
8d1c484d443d317fc05ee83f426c83fa
Sources:
SUSE LINUX 10.1:
0b6ab9aba01fb96057457dfa029075c6
SUSE LINUX 10.0:
22d3bccb56fade850da7f816f1b482f2
SUSE LINUX 9.3:
1535c2f49679dac17b60199e3f447121
SUSE LINUX 9.2:
0a33023485fbdd877595ad66e541d06c
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
Please restart all applications using libtiff. Desktop users should logout
and re-login.
On server systems you have to restart all server applications manually.
______________________________________________________________________________
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.
====================================================================
