-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: XFree86, Xorg
Announcement ID: SUSE-SA:2007:027
Date: Fri, 20 Apr 2007 17:00:00 +0000
Affected Products: SUSE LINUX 9.3
SUSE LINUX 10.0
SUSE LINUX 10.1
openSUSE 10.2
UnitedLinux 1.0
SuSE Linux Enterprise Server 8
SuSE Linux Openexchange 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
Open Enterprise Server
Novell Linux POS 9
SUSE SLED 10
SLE SDK 10
SUSE SLES 10
Vulnerability Type: local privilege escalation
Severity (1-10): 7
SUSE Default Package: yes
Cross-References: CVE-2007-1003, CVE-2007-1351, CVE-2007-1352
CVE-2007-1667
Content of This Advisory:
1) Security Vulnerability Resolved:
Several X security problems
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
Several X security problems were fixed that could be used by local
attackers to crash the X server or potentially to execute code as
root user.
- CVE-2007-1003: Integer overflows in the XC-MISC extension of the
X-server could potentially be exploited to execute code with root
privileges.
- CVE-2007-1667: Integer overflows in libX11 could cause crashes.
- CVE-2007-1352, CVE-2007-1351: Integer overflows in the font handling
of the X-server could potentially be exploited to execute code with
root privileges.
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
Please close and restart all running instances of X after the update.
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:
f653bfd1f2d272f42bfed24c6eeb1971
dbc88177adc2c4e061cc698ac16942b7
90189f0fabe1a25f97ee3717fe73a268
3ab84eb3fc151fce81b71b0834e0982e
SUSE LINUX 10.1:
d81eceaf06b90d1f48c4e2138a94cb48
0aaf70eee9f9429e7472e340a368ac74
c00a864032826956a1e0c99bf1ed6fc7
6cd779e78b4cd4d9a7e6ffe0b3394bcd
3979722de546dbc5accb94860db7e367
6ea5413c97893e21c273b53278dfd166
SUSE LINUX 10.0:
24e662286dad295b861990479564bbc6
d2eebfa2b0ecc7648ed55ed81e6e6ca0
1883fead459c79ad1b8f4a1742431029
2a1feeeb929b9407c94ccea5b4798bdc
647f7deea79edc9cb1bd75e42b9c36fa
7371693bab6474b4eba84450c47e9856
SUSE LINUX 9.3:
9a1f51d708a343686924457782eb40ff
1544af7ebe5cde6e03f78219e15fe329
09689cf5bd8c8a1ffea4324f6b1c797a
c7ec29ab8f7902a825cb060caa930dc5
455b252e226a2977bcc0c95eddb05f89
dfaf184254c76d904ca463459c696070
Power PC Platform:
openSUSE 10.2:
2dd0ac059f850919219f05f7a26dbbf1
125f5130a49ec611c457221fb7565176
14e0e29390a097d158ce5fe2cfbe5afd
213df9034f5bbaef13bc5d0c901ba3ec
SUSE LINUX 10.1:
415790c7a0a4aa40e6408f1c27821dc4
7fabe65e827fb30a429b56a138351bbf
41eae3160142eb46385dbe5baf89c408
c8116ab4d95c2fdff2ec4da37e601799
b4461725823fa145077cc0413d1da591
31035241df2327b3e5a51c6c160f2274
SUSE LINUX 10.0:
569448ec158732114dea533ca251d8d0
00c7188efcf7910ba9e4eb3f5a530b83
b8dc14d51b4f1f5826fd2b9c38c9b95a
51773cd8ec74d6dcf940421198185caa
f4aec18ae21bdd197bcd9ca747fff6af
01d581f8a368bb1851bc9dce18e17e74
x86-64 Platform:
openSUSE 10.2:
d5279a52559dad95051d35152299bca0
1a8a0d3686577c2659489f9db15fc33a
f67e112ae3a9a86738fb24c18a37f923
56a914585e7c13a4dbbff4442e1d1b68
deb38a3c779aa555eaf2945d481fbb71
92cf365d5c7a8fe64f597f6c905029cb
SUSE LINUX 10.1:
de5abacece46c45c2638560186856d20
5467552ff02f20f0cd853b117b78d973
618d2dcaaa6ddc4b42af897cc5fda760
3ac80b6b207d816ebce3a5ed28f3680c
e30fba61063b8db8356372a95eb2d75b
bb58d46daab8f11f7ab956c696b19f40
4ad6d5a0e3b1da87b4875870294a668e
SUSE LINUX 10.0:
152bf582064aedb118ba39608694af90
64f5d9e1e1a8fa1c6bdea1f7f2c567b8
a6ae6668b4a4cbf4aa43148494f5ecea
b2b4869419f0e9a454b866d14105094b
e5c1529ea2ebaaf60b05217264da6bea
ad624932ecc4dbf72027de821c7f3924
bbe45bab4874a15923e17bb9e33381ee
SUSE LINUX 9.3:
fb82e0eaff5175dff0b2aef08db85b7b
54adc63d83c7c35b0f93eab346cc5022
c451aba3b6f8bb0fd3a9fb3c47e7f9dd
215572fb3d47192393536977bddcf11f
06c442986173694140ca4f8fa07c971c
96617ce6e2bce28d30bc3e1609f2cd1d
4bbae390f12493c1d49a463f99849b68
Sources:
openSUSE 10.2:
ce37a23d3e6647f0af0b3e11e5b45c70
09035566ccd0ccd3245e00b8a9b20762
632b8e481383561cea9688228dd3e2b4
8333f36d72e191828c30c445ac3a081d
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
UnitedLinux 1.0
http://support.novell.com/techcenter/psdb/d01bb675582b3827d7dea897df29019c.html
SuSE Linux Openexchange Server 4
http://support.novell.com/techcenter/psdb/d01bb675582b3827d7dea897df29019c.html
SuSE Linux Enterprise Server 8
http://support.novell.com/techcenter/psdb/d01bb675582b3827d7dea897df29019c.html
SuSE Linux Standard Server 8
http://support.novell.com/techcenter/psdb/d01bb675582b3827d7dea897df29019c.html
SuSE Linux School Server
http://support.novell.com/techcenter/psdb/d01bb675582b3827d7dea897df29019c.html
SUSE LINUX Retail Solution 8
http://support.novell.com/techcenter/psdb/d01bb675582b3827d7dea897df29019c.html
Open Enterprise Server
http://support.novell.com/techcenter/psdb/d02caf41ef1474e8a88dc11ae5b1e0ef.html
Novell Linux POS 9
http://support.novell.com/techcenter/psdb/d02caf41ef1474e8a88dc11ae5b1e0ef.html
Novell Linux Desktop 9
http://support.novell.com/techcenter/psdb/d02caf41ef1474e8a88dc11ae5b1e0ef.html
SuSE Linux Desktop 1.0
http://support.novell.com/techcenter/psdb/d02caf41ef1474e8a88dc11ae5b1e0ef.html
SUSE SLES 9
http://support.novell.com/techcenter/psdb/d02caf41ef1474e8a88dc11ae5b1e0ef.html
SUSE SLES 10
http://support.novell.com/techcenter/psdb/8476a77bfebd56f3cd855c67d62ee674.html
SLE SDK 10
http://support.novell.com/techcenter/psdb/8476a77bfebd56f3cd855c67d62ee674.html
SUSE SLED 10
http://support.novell.com/techcenter/psdb/8476a77bfebd56f3cd855c67d62ee674.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.
====================================================================
