First published: Fri Sep 23 2011(Updated: )
It was reported [1] that a number of GLX X calls were lacking proper input sanitization. This could allow an attacker with access to the GLX calls to crash the X server or, possibly, execute arbitrary code within it (typically, this would just be the logged in user). These were fixed in upstream git [2] with the following commits: 402b329c3aa8ddbebaa1f593306a02d4cd6fed26 1137c11be0f82049d28024eaf963c6f76e0d4334 a883cf1545abd89bb2cadfa659718884b56fd234 d9225b9602c85603ae616a7381c784f5cf5e811c 62319e8381ebd645ae36b25e5fc3c0e9b098387b 6c69235a9dfc52e4b4e47630ff4bab1a820eb543 ec9c97c6bf70b523bc500bd3adf62176f1bb33a4 3f0d3f4d97bce75c1828635c322b6560a45a037f [1] <a href="https://bugs.freedesktop.org/show_bug.cgi?id=28823">https://bugs.freedesktop.org/show_bug.cgi?id=28823</a> [2] <a href="http://cgit.freedesktop.org/xorg/xserver">http://cgit.freedesktop.org/xorg/xserver</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
X.org X.org | =1.7.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.