-----BEGIN PGP SIGNED MESSAGE-----
______________________________________________________________________________
SUSE Security Announcement
Package: xine-ui,xine-lib,xine-extra,xine-devel
Announcement ID: SUSE-SA:2007:013
Date: Tue, 23 Jan 2007 08:00:00 +0000
Affected Products: SUSE LINUX 9.3
SUSE LINUX 10.0
SUSE LINUX 10.1
openSUSE 10.2
SUSE SLED 10
SLE SDK 10
Vulnerability Type: remote code execution
Severity (1-10): 4
SUSE Default Package: no
Cross-References: CVE-2007-0017
Content of This Advisory:
1) Security Vulnerability Resolved:
format string bug
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
This update fixes several format string bugs that can be exploited remotely
with user-assistance to execute arbitrary code.
Since SUSE Linux version 10.1 format string bugs are not exploitable
anymore. (CVE-2007-0017)
2) Solution or Work-Around
No temporary work-around known.
3) Special Instructions and Notes
none
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:
openSUSE 10.2:
2cacbb4f4e177362149518481480165a
73cbdd8d443596547875804bd8e2ca8f
2114f7c6a4c8351adab588c173419778
5d4dd945a812ba0b17619c267ec8f2b5
SUSE LINUX 10.1:
3eb1465401e5e1c6f36d8e2d7ca3e114
e2fbf53b629e835dbc2558e87fabf926
d710db4b4d20f7ea4485d16845cb4be2
SUSE LINUX 10.0:
06753ebd3608223077c95c01f8bc3122
60ab4fd7c193d687d9484e5691aa3f01
4bc3f28d7e600fbb78c65f6b0dcfc436
SUSE LINUX 9.3:
c944ed72f913771f0c2300883573e111
cee2a8a9669b429dde4e465e83aae70f
Power PC Platform:
openSUSE 10.2:
a1fcfa82deed685446a213439639a579
bc2dcf2266dbb56b1a0291209aad2dd7
SUSE LINUX 10.1:
c337440571123263478dd2a64059a4e8
3cf476901522d7b5abd5bf3cb18484a9
a9e762bad246963a7564c1f36a5f0392
SUSE LINUX 10.0:
930dc314de3ab49a8655e6cdb89ff50d
ddd255708abfb433a3497d790491be55
827125d558472b685f0f1843d0eb3850
x86-64 Platform:
openSUSE 10.2:
1dac6b23d257670ca7182f018c12a69b
11dae8e2ecb5a78eb6b1cd39713f6322
519480f44a28d4e3cab37aceca7e7c13
3b5db06dab41a4ff2a53d22b3f6f6238
b1a06bf5fd93c905bf5008859c88690d
aa85b56d559aca4960693bad80a451bd
SUSE LINUX 10.1:
72f6cfc29f428a5d7dc40fbcb285cfe6
34382ef5b0ec94524678bdf842a21ecb
316fd37892ef25073cf9d6ae11fb510b
ee0a3ce52f3bf431ced82dbd0148890c
SUSE LINUX 10.0:
83094481db18fb55447a19b86db281ff
0e1b36454127be6815d1f52325ee1a70
45829c44efd83afaefe570d81f8a7568
bfe5d54a07d28cb9fef528c0257d4db7
SUSE LINUX 9.3:
e829f9cbd5e02a0498f03a2180b57963
064665c8b3ac38f71634734c101f1602
8e7011003db37a1799bbd531ae957a28
Sources:
openSUSE 10.2:
f92b96c21a6e45ede2faa81c9efade83
ed0382a57f117bcf04236ca660092afe
SUSE LINUX 10.1:
1d347a598b2e8dfc5eaa4f7b9c951242
SUSE LINUX 10.0:
d1d2036b46056a00b3c5a0cee5371ad8
SUSE LINUX 9.3:
02ae3f6c9a88ec0aabcce701bba20542
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
SLE SDK 10
http://support.novell.com/techcenter/psdb/3850f4cb30959892275d84ebf0b1dfc6.html
SUSE SLED 10
http://support.novell.com/techcenter/psdb/3850f4cb30959892275d84ebf0b1dfc6.html
______________________________________________________________________________
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:
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.
====================================================================
