Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 18 Apr 2012 13:37:21 -0700
From: Kees Cook <>
To: Kurt Seifried <>
Subject: Re: CVE request: Xorg input device format string flaw

On Wed, Apr 18, 2012 at 1:23 PM, Kurt Seifried <> wrote:
> On 04/18/2012 01:28 PM, Kees Cook wrote:
>> Hello,
>> Adding an input device with a malicious name can trigger a format
>> string flaw in Xorg's logging subsystem. For builds of Xorg
>> lacking -D_FORTIFY_SOURCE=2 (or 32-bit systems lacking the fix to
>> fortify[1]) this can lead to arbitrary code execution as the Xorg
>> user, usually root. When built with fortify, this is a denial of
>> service, since Xorg will abort.
>> Proposed solution patch series can be found here: 1/4
>> 2/4
>> 3/4
>> 4/4
>> -Kees
>> [1]
> So
> are you asking for just the device name issue covered in

Yeah, but I wanted to point to the entire patch series, since that
fix, I think, depends on pieces from the others.


Kees Cook
Chrome OS Security

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.