SUSE Security Announcement: freetype2 (SUSE-SA:2007:041)

PGP SIGNED MESSAGE
Hash: SHA1



SUSE Security Announcement

Package: freetype2
Announcement ID: SUSE-SA:2007:041
Date: Wed, 04 Jul 2007 14:00:00 +0000
Affected Products: SUSE LINUX 10.0
SUSE LINUX 10.1
openSUSE 10.2
UnitedLinux 1.0
SuSE Linux Enterprise Server 8
SuSE Linux Server 4
SuSE Linux Desktop 1.0
SuSE Linux Standard Server 8
SuSE Linux School Server
SUSE LINUX Retail Solution 8
SUSE SLES 9
Novell Linux Desktop 9
Enterprise Server
Novell Linux PS 9
SUSE Linux Enterprise Desktop 10 SP1
SUSE Linux Enterprise Server 10 SP1
Vulnerability Type: remote code execution
Severity (1-10): 8
SUSE Default Package: yes
Cross-References: CVE-2007-2754

Content of This Advisory:
1) Security Vulnerability Resolved:
freetype2 security problem
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

The TTF rendering library freetype2 was updated to fix an integer
signedness bug when handling TTF images.

This bug can lead to a heap overflow that can be exploited to execute
arbitrary code. (CVE-2007-2754)

Updates for SLE 10 Service Pack 1 and SUSE Linux 10.1 were released on
Monday the 2nd of July, all other products received them at June 20th.

2) Solution or Work-Around

There is no known workaround, please install the update packages.

3) Special Instructions and Notes

Please close and restart your desktop after the update.

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:

openSUSE 10.2:





SUSE LINUX 10.1:





SUSE LINUX 10.0:





Power PC Platform:

openSUSE 10.2:





SUSE LINUX 10.1:





SUSE LINUX 10.0:





x86-64 Platform:

openSUSE 10.2:









SUSE LINUX 10.1:









SUSE LINUX 10.0:









Sources:

openSUSE 10.2:



SUSE LINUX 10.1:



SUSE LINUX 10.0:



maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:

SUSE Linux Enterprise Server 10 SP1


SUSE Linux Enterprise Desktop 10 SP1


UnitedLinux 1.0


SuSE Linux Server 4


Enterprise Server


Novell Linux PS 9


Novell Linux Desktop 9


SuSE Linux Enterprise Server 8


SuSE Linux Standard Server 8


SuSE Linux School Server


SUSE LINUX Retail Solution 8


SuSE Linux Desktop 1.0


SUSE SLES 9




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:

opensuse-security (AT) opensuse (DOT) org
- General Linux and SUSE security discussion.
All SUSE security announcements are sent to this list.
To subscribe, send an e-mail to
<opensuse-security+subscribe (AT) opensuse (DOT) org>.

opensuse-security-announce (AT) opensuse (DOT) org
- SUSE's announce-only mailing list.
SUSE's security announcements are sent to this list.
To subscribe, send an e-mail to
<@opensuse.org>.


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.5 (GNU/Linux)





+

=GRor
PGP SIGNATURE
--
To unsubscribe, e-mail: @opensuse.org
For additional commands, e-mail: @opensuse.org