From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] xserver_xorg-server: add upstream security fixes for CVE-2017-10971 / 10972
Date: Wed, 19 Jul 2017 15:58:54 +0200 [thread overview]
Message-ID: <8760eoa5pd.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170710070752.16623-1-peter@korsgaard.com> (Peter Korsgaard's message of "Mon, 10 Jul 2017 09:07:52 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Add upstream patches fixing the following security issues:
> CVE-2017-10971:
> The endianess handling for X Events assumed a fixed size of X Event structures and
> had a specific 32 byte stack buffer for that.
> However "GenericEvents" can have any size, so if the events were sent in the wrong
> endianess, this stack buffer could be overflowed easily.
> So authenticated X users could overflow the stack in the X Server and with the X
> server usually running as root gaining root prileveges.
> CVE-2017-10972:
> An information leak out of the X server due to an uninitialized stack area when swapping
> event endianess.
> For more details, see the advisory:
> http://www.openwall.com/lists/oss-security/2017/07/06/6
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2017.02.x and 2017.05.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-07-19 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 7:07 [Buildroot] [PATCH] xserver_xorg-server: add upstream security fixes for CVE-2017-10971 / 10972 Peter Korsgaard
2017-07-11 19:32 ` Peter Korsgaard
2017-07-19 13:58 ` Peter Korsgaard [this message]
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=8760eoa5pd.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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