From: Dieken <Dieken@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] X.org vulnerability and releases
Date: Sun, 02 Apr 2023 10:51:05 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43174@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]
New issue by Dieken on void-packages repository
https://github.com/void-linux/void-packages/issues/43174
Description:
https://github.com/void-linux/void-packages/blob/836b6c484e0b9de2f0f9b8ac2f646e99136e56e8/srcpkgs/xorg-server/template#L3
https://github.com/void-linux/void-packages/blob/836b6c484e0b9de2f0f9b8ac2f646e99136e56e8/srcpkgs/xorg-server-xwayland/template#L3
https://lwn.net/Articles/927887/
The X.Org project has [announced](https://lists.x.org/archives/xorg-announce/2023-March/003374.html) a vulnerability in its X server and Xwayland (CVE-2023-1393).
> This issue can lead to local privileges elevation on systems where the X server is running privileged and remote code execution for ssh X forwarding sessions.
>
> [...] If a client explicitly destroys the compositor overlay window (aka COW), the Xserver would leave a dangling pointer to that window in the CompScreen structure, which will trigger a use-after-free later.
That has led to the release of [xorg-server 21.1.8](https://lists.x.org/archives/xorg-announce/2023-March/003377.html), [xwayland 22.1.9](https://lists.x.org/archives/xorg-announce/2023-March/003375.html), and [xwayland 23.1.1](https://lists.x.org/archives/xorg-announce/2023-March/003376.html).
next reply other threads:[~2023-04-02 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 8:51 Dieken [this message]
2023-04-02 14:21 ` [ISSUE] [CLOSED] " Dieken
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43174@inbox.vuxu.org \
--to=dieken@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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;
as well as URLs for NNTP newsgroup(s).