-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: Xorg and XFree
Announcement ID: SUSE-SA:2008:003
Date: Thu, 17 Jan 2008 15:00:00 +0000
Affected Products: SUSE LINUX 10.1
openSUSE 10.2
openSUSE 10.3
SuSE Linux Enterprise Server 8
SUSE SLES 9
Novell Linux Desktop 9
Open Enterprise Server
Novell Linux POS 9
SUSE Linux Enterprise Desktop 10 SP1
SLE SDK 10 SP1
SUSE Linux Enterprise Server 10 SP1
Vulnerability Type: remote code execution
Severity (1-10): 7
SUSE Default Package: yes
Cross-References: CVE-2007-5760
CVE-2007-5958
CVE-2007-6427
CVE-2007-6428
CVE-2007-6429
CVE-2008-0006
Content of This Advisory:
1) Security Vulnerability Resolved:
fix of several vulnerabilities
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 X windows system is vulnerable to several kind of vulner-
abilities that are caused due to insufficient input validation.
The bugs range from crashing the X server to executing arbitrary
code with the privilges of the X server process.
For a successful attack the opponent needs shell access to the
vulnerable system (local) or an already established connection
to the X server.
Thanks to US CERT and iDefense for reporting this vulnerabilities
and to the Xorg-Security folks for fixing it.
The Fixes are:
- CVE-2007-5760: XFree86 Misc extension out of bounds array index
- CVE-2007-5958: File existence disclosure
- CVE-2007-6427: Xinput extension memory corruption
- CVE-2007-6428: TOG-cup extension memory corruption
- CVE-2007-6429: MIT-SHM and EVI extensions integer overflows
- CVE-2008-0006: PCF Font parser buffer overflow
2) Solution or Work-Around
none
3) Special Instructions and Notes
Please restart your X server. (logout and login)
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.3:
4bbe5643ab5197a9cc685e4223190447
4cce05a6c93d4bf6a862fb5a69bccb8b
4a01021996233c6e2ff490fad5aec03e
97836a761ae467f19d94d1b91ea9b995
5ff972aaa94b837d8d62317c6bacc88d
openSUSE 10.2:
a3246ccdce33d8110f342bdbb2585310
d60e0060e406b75e3ac71210ab8ff0fa
92d31c20ae082e9188aecd45a9a6d03e
a4d4d9255140056e46cb38d0e2d3c6d6
SUSE LINUX 10.1:
c9938a12824aeb3fd74d49d26ce20b77
312edac7fcafa8c418f183d8a18c36eb
10bbd9107fdaf0dd5279044161d20a0b
a91dabea7a3c491e2388b3b246be06c2
064c1a03036ad7679def77653acde9df
Power PC Platform:
openSUSE 10.3:
6fdb46c5be13610d18c1cb0b301d4d12
617dade18d68a52f3b58d38b59031415
f3cfb22666dd58a26af56354250e6636
b9f0fec937301505361978b745f40ad7
e0ca4a975175a9e13b99a33e79545ad2
openSUSE 10.2:
80e857e61d1f1a7b540127ffcfdca0ee
b4991e6eb90fcea9afc83ee1831b8986
879a225b74608634cda54139aaf6a0ae
f1e0439b2acfe584d008491d1fa390a2
SUSE LINUX 10.1:
e5012a1fdff71ced7a53827f05d0727a
33873e20b3f5918eb36908f3a1f5d07a
2f1dcc7e26c4a9fbde3edd89bc994238
14fcd28cd5078d76ae67a1db33ca45bc
8ca0ddaac627503f029f72d7671273b2
x86-64 Platform:
openSUSE 10.3:
d5452701eb0d6f9ef91d1c2264e5c716
e19652d7217db93081f303a3131cf845
e814f811a5ad43cc3abcde619c2779d4
599758d0f90e6b4c0527206daa776866
0a9224a7eabef9caa9b37b54b8caf05c
9a533681e8d32525b1a92e678ca32d73
a4b50a22158bafd13104472abde095d0
openSUSE 10.2:
58024c63be1540f240bc6100697f5b9a
19a58ca74eb67a143de3fe352aee062f
c2e37d9cc52e979bf73e8a4f34884b1f
e8af19e6ad8b263e8040fa58d5099e35
14a34bc8259984d3fdd5748117260b0b
58aa334590da306353375b1830a717ee
SUSE LINUX 10.1:
52853afb62f85a7a99978b9467d68844
d69e56bc7042e92e484580068585e7d5
ed7645afff6fee4b0c51ec89038c39da
ba857d6ca557ea04e744f4257b22380e
26d99f7fd46c3b2d2b622d3b87db7325
9d5215fad591bca1fd4d9348ded346f8
4afae475777e64990502d839de5b1eb1
Sources:
openSUSE 10.3:
de839a08105c51acc7887426bde824b2
6d1776ab401f80cc697a8c6e2857df26
openSUSE 10.2:
d615319400643142258e964b02409cfe
8d0e28dd0d5b02b0d473284fccae86a9
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
SuSE Linux Enterprise Server 8
SLE SDK 10 SP1
http://support.novell.com/techcenter/psdb/18a56e9d8d46b54d240bd74f97e7a881.html
SUSE Linux Enterprise Server 10 SP1 for IBM zSeries 64bit
http://support.novell.com/techcenter/psdb/677761c3a6779efbab4567360d1ec13c.html
SUSE Linux Enterprise Server 10 SP1
http://support.novell.com/techcenter/psdb/18a56e9d8d46b54d240bd74f97e7a881.html
http://support.novell.com/techcenter/psdb/677761c3a6779efbab4567360d1ec13c.html
http://support.novell.com/techcenter/psdb/e4b2229c714a9c6fb576185356d86fc8.html
SUSE Linux Enterprise Desktop 10 SP1
http://support.novell.com/techcenter/psdb/18a56e9d8d46b54d240bd74f97e7a881.html
http://support.novell.com/techcenter/psdb/e4b2229c714a9c6fb576185356d86fc8.html
Open Enterprise Server
http://support.novell.com/techcenter/psdb/686ed843d1dc7672badd026d1d0712c1.html
http://support.novell.com/techcenter/psdb/56240f6955337ddf455d2aa23797006a.html
Novell Linux POS 9
http://support.novell.com/techcenter/psdb/686ed843d1dc7672badd026d1d0712c1.html
http://support.novell.com/techcenter/psdb/56240f6955337ddf455d2aa23797006a.html
Novell Linux Desktop 9
http://support.novell.com/techcenter/psdb/686ed843d1dc7672badd026d1d0712c1.html
http://support.novell.com/techcenter/psdb/56240f6955337ddf455d2aa23797006a.html
SUSE SLES 9
http://support.novell.com/techcenter/psdb/ce66af7045437b3b5756995a1909aa37.html
http://support.novell.com/techcenter/psdb/686ed843d1dc7672badd026d1d0712c1.html
http://support.novell.com/techcenter/psdb/56240f6955337ddf455d2aa23797006a.html
SuSE Linux Enterprise Server 8 for x86
______________________________________________________________________________
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
.
opensuse-security-announce@opensuse.org
- 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.
====================================================================
