-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: libgsf
Announcement ID: SUSE-SA:2006:076
Date: Thu, 14 Dec 2006 12:00:00 +0000
Affected Products: Novell Linux Desktop 9
Novell Linux POS 9
Open Enterprise Server
SUSE LINUX 10.1
SUSE LINUX 10.0
SUSE LINUX 9.3
SuSE Linux Desktop 1.0
SUSE SLED 10
SUSE SLES 10
SUSE SLES 9
Vulnerability Type: remote code execution
Severity (1-10): 8
SUSE Default Package: yes
Cross-References: CVE-2006-4514
Content of This Advisory:
1) Security Vulnerability Resolved:
libgsf buffer 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:
See SUSE Security Summary Report.
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
The libgsf library is used by various GNOME programs to handle for
instance OLE2 data streams.
Specially crafted OLE documents enabled attackers to use a heap buffer
overflow for potentially executing code.
This issue is tracked by the Mitre CVE ID CVE-2006-4514.
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
Please close and restart applications using libgsf.
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:
91b1e160b88a4da68781ca4391a0aa7b
SUSE LINUX 10.0:
6b4e5b5ed0e564769a0bb3d0e288b8be
SUSE LINUX 9.3:
48555a9c645cae527bdc5315251d662f
Power PC Platform:
SUSE LINUX 10.1:
d8c05b0415c9e196c2d1a8cc42ac0402
SUSE LINUX 10.0:
24e8d5c92f635db2ef3049339ba1754b
x86-64 Platform:
SUSE LINUX 10.1:
6f8ebb0842088a321a15192480a5388d
bab0e91a620413c92e403bcfdd6d7147
SUSE LINUX 10.0:
f9992beea6a3fe27204ebee475ba8234
b1369a901898a1bfb9fd5ba643dd7291
SUSE LINUX 9.3:
02e536160da1597a38153d1643de00b4
abb66f3f4f3b3cd34382612805878466
Sources:
SUSE LINUX 10.1:
0b386df6f643991c71d61dbf07d448fe
SUSE LINUX 10.0:
455b6c354c40ac3157a158b8902238c2
SUSE LINUX 9.3:
7b6bb054f79babd4893be99c331eab2f
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
Open Enterprise Server
http://support.novell.com/techcenter/psdb/8925f151052752a744fcfe7924249f34.html
Novell Linux POS 9
http://support.novell.com/techcenter/psdb/8925f151052752a744fcfe7924249f34.html
Novell Linux Desktop 9
http://support.novell.com/techcenter/psdb/8925f151052752a744fcfe7924249f34.html
SuSE Linux Desktop 1.0
http://support.novell.com/techcenter/psdb/8925f151052752a744fcfe7924249f34.html
SUSE SLES 10
http://support.novell.com/techcenter/psdb/8925f151052752a744fcfe7924249f34.html
SUSE SLED 10
http://support.novell.com/techcenter/psdb/8925f151052752a744fcfe7924249f34.html
SUSE SLES 9
http://support.novell.com/techcenter/psdb/8925f151052752a744fcfe7924249f34.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:
opensuse-security@opensuse.org
- 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
.
==================================================================== SUSE's security contact is or .
The public key is listed below.
====================================================================
