From: Pierre-Yves Rofes <py@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Cc: full-disclosure@lists.grok.org.uk, bugtraq@securityfocus.com,
security-alerts@linuxsecurity.com
Subject: [gentoo-announce] [ GLSA 200710-16 ] X.Org X server: Composite local privilege escalation
Date: Mon, 15 Oct 2007 00:38:27 +0200 [thread overview]
Message-ID: <47129A63.4060602@gentoo.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 200710-16
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: High
Title: X.Org X server: Composite local privilege escalation
Date: October 14, 2007
Bugs: #191964
ID: 200710-16
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
A vulnerability has been discovered in the Composite extension of the
X.Org X server, allowing for a local privilege escalation.
Background
==========
The X Window System is a graphical windowing system based on a
client/server model.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 x11-base/xorg-server < 1.3.0.0-r1 >= 1.3.0.0-r1
Description
===========
Aaron Plattner discovered a buffer overflow in the compNewPixmap()
function when copying data from a large pixel depth pixmap into a
smaller pixel depth pixmap.
Impact
======
A local attacker could execute arbitrary code with the privileges of
the user running the X server, typically root.
Workaround
==========
Disable the Composite extension by setting ' Option "Composite"
"disable" ' in the Extensions section of xorg.conf.
Note: This could affect the functionality of some applications.
Resolution
==========
All X.Org X server users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-base/xorg-server-1.3.0.0-r1"
References
==========
[ 1 ] CVE-2007-4730
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-4730
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
http://security.gentoo.org/glsa/glsa-200710-16.xml
Concerns?
=========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
http://bugs.gentoo.org.
License
=======
Copyright 2007 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.
http://creativecommons.org/licenses/by-sa/2.5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHEppiuhJ+ozIKI5gRAmOeAJ46xK+4nH8LWGxbNmnlmPrltBqsHgCfUTNK
8qUzM6SvnXk2c2yZgp50GTk=
=DiOR
-----END PGP SIGNATURE-----
--
gentoo-announce@gentoo.org mailing list
reply other threads:[~2007-10-14 23:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47129A63.4060602@gentoo.org \
--to=py@gentoo.org \
--cc=bugtraq@securityfocus.com \
--cc=full-disclosure@lists.grok.org.uk \
--cc=gentoo-announce@lists.gentoo.org \
--cc=security-alerts@linuxsecurity.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox