VuXML ID | Description |
96d84238-b500-490b-b6aa-2b77090a0410 | xorg-server -- Overlay Window Use-After-Free
The X.Org project reports:
- ZDI-CAN-19866/CVE-2023-1393: X.Org Server Overlay Window Use-After-Free
Local Privilege Escalation Vulnerability
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.
Discovery 2023-03-29 Entry 2023-03-29 xorg-server
xephyr
xorg-vfbserver
< 21.1.8,1
xorg-nestserver
< 21.1.8,2
xwayland
>= 23.0.0,1 lt 23.1.1,1
< 22.1.9,1
xwayland-devel
< 21.0.99.1.439
https://lists.x.org/archives/xorg-announce/2023-March/003374.html
CVE-2023-1393
|
800e8bd5-3acb-11dd-8842-001302a18722 | xorg -- multiple vulnerabilities
Matthieu Herrb of X.Org reports:
Several vulnerabilities have been found in the server-side code
of some extensions in the X Window System. Improper validation of
client-provided data can cause data corruption.
Exploiting these overflows will crash the X server or,
under certain circumstances allow the execution of arbitray machine
code.
When the X server is running with root privileges (which is the case
for the Xorg server and for most kdrive based servers), these
vulnerabilities can thus also be used to raise privileges.
All these vulnerabilities, to be exploited successfully, require either
an already established connection to a running X server (and normally
running X servers are only accepting authenticated connections), or a
shell access with a valid user on the machine where the vulnerable
server is installed.
Discovery 2008-06-11 Entry 2008-06-15 xorg-server
< 1.4.2,1
CVE-2008-1377
CVE-2008-1379
CVE-2008-2360
CVE-2008-2361
CVE-2008-2362
http://lists.freedesktop.org/archives/xorg/2008-June/036026.html
http://secunia.com/advisories/30627/
|
ffa15b3b-e6f6-11ea-8cbf-54e1ad3d6335 | xorg-server -- Multiple input validation failures in X server extensions
The X.org project reports:
All theses issuses can lead to local privileges elevation on
systems where the X server is running privileged.
The handler for the XkbSetNames request does not validate the
request length before accessing its contents.
An integer underflow exists in the handler for the
XIChangeHierarchy request.
An integer underflow exist in the handler for the XkbSelectEvents
request.
An integer underflow exist in the handler for the CreateRegister
request of the X record extension.
Discovery 2020-08-25 Entry 2020-08-25 xorg-server
< 1.20.8_4,1
xephyr
< 1.20.8_4,1
xorg-vfbserver
< 1.20.8_4,1
xorg-nestserver
< 1.20.8_4,1
xwayland
< 1.20.8_4,1
xorg-dmx
< 1.20.8_4,1
CVE-2020-14345
CVE-2020-14346
CVE-2020-14361
CVE-2020-14362
https://lists.x.org/archives/xorg-announce/2020-August/003058.html
|
3c7ba82a-d3fb-11ea-9aba-0c9d925bbbc0 | xorg-server -- Pixel Data Uninitialized Memory Information Disclosure
The X.org project reports:
Allocation for pixmap data in AllocatePixmap() does not initialize
the memory in xserver, it leads to leak uninitialize heap memory to
clients. When the X server runs with elevated privileges.
This flaw can lead to ASLR bypass, which when combined with other
flaws (known/unknown) could lead to lead to privilege elevation in
the client.
Discovery 2020-07-31 Entry 2020-08-01 xorg-server
< 1.20.8_3,1
xephyr
< 1.20.8_3,1
xorg-vfbserver
< 1.20.8_3,1
xorg-nestserver
< 1.20.8_3,1
xwayland
< 1.20.8_3,1
xorg-dmx
< 1.20.8_3,1
https://lists.x.org/archives/xorg-announce/2020-July/003051.html
CVE-2020-14347
|
27b9b2f0-8081-11e4-b4ca-bcaec565249c | xserver -- multiple issue with X client request handling
Alan Coopersmith reports:
Ilja van Sprundel, a security researcher with IOActive, has
discovered a large number of issues in the way the X server
code base handles requests from X clients, and has worked
with X.Org's security team to analyze, confirm, and fix
these issues.
The vulnerabilities could be exploited to cause the X server
to access uninitialized memory or overwrite arbitrary memory
in the X server process. This can cause a denial of service
(e.g., an X server segmentation fault), or could be exploited
to achieve arbitrary code execution.
The GLX extension to the X Window System allows an X client
to send X protocol to the X server, to request that the X
server perform OpenGL rendering on behalf of the X client.
This is known as "GLX indirect rendering", as opposed to
"GLX direct rendering" where the X client submits OpenGL
rendering commands directly to the GPU, bypassing the X
server and avoiding the X server code for GLX protocol
handling.
Most GLX indirect rendering implementations share some
common ancestry, dating back to "Sample Implementation"
code from Silicon Graphics, Inc (SGI), which SGI
originally commercially licensed to other Unix workstation
and graphics vendors, and later released as open source, so
those vulnerabilities may affect other licensees of SGI's
code base beyond those running code from the X.Org Foundation
or the XFree86 Project.
Discovery 2014-12-09 Entry 2014-12-10 xorg-server
< 1.12.4_10,1
http://lists.x.org/archives/xorg-announce/2014-December/002500.html
CVE-2014-8091
CVE-2014-8092
CVE-2014-8093
CVE-2014-8094
CVE-2014-8095
CVE-2014-8096
CVE-2014-8097
CVE-2014-8098
CVE-2014-8099
CVE-2014-8100
CVE-2014-8101
CVE-2014-8102
|
54a69cf7-b2ef-11e4-b1f1-bcaec565249c | xorg-server -- Information leak in the XkbSetGeometry request of X servers.
Peter Hutterer reports:
Olivier Fourdan from Red Hat has discovered a protocol handling
issue in the way the X server code base handles the XkbSetGeometry
request.
The issue stems from the server trusting the client to send valid
string lengths in the request data. A malicious client with string
lengths exceeding the request length can cause the server to copy
adjacent memory data into the XKB structs. This data is then
available to the client via the XkbGetGeometry request. The
data length is at least up to 64k, it is possible to obtain
more data by chaining strings, each string length is then
determined by whatever happens to be in that 16-bit region of
memory.
A similarly crafted request can likely cause the X server
to crash.
Discovery 2015-02-10 Entry 2015-02-12 xorg-server
< 1.14.7_2,1
xorg-server
>= 1.15.0,1 lt 1.16.4,1
CVE-2015-0255
http://lists.freedesktop.org/archives/xorg/2015-February/057158.html
|
972568d6-3485-40ab-80ff-994a8aaf9683 | xorg-server -- Multiple vulnerabilities
The X.Org project reports:
- CVE-2023-6377/ZDI-CAN-22412/ZDI-CAN-22413: X.Org
server: Out-of-bounds memory write in XKB button actions
A device has XKB button actions for each button on the
device. When a logical device switch happens (e.g. moving
from a touchpad to a mouse), the server re-calculates the
information available on the respective master device
(typically the Virtual Core Pointer). This re-calculation
only allocated enough memory for a single XKB action
rather instead of enough for the newly active physical
device's number of button. As a result, querying or
changing the XKB button actions results in out-of-bounds
memory reads and writes.
This may lead to local privilege escalation if the server is run as root or
remote code execution (e.g. x11 over ssh).
- CVE-2023-6478/ZDI-CAN-22561: X.Org server:
Out-of-bounds memory read in RRChangeOutputProperty and
RRChangeProviderProperty
This fixes an OOB read and the resulting information disclosure.
Length calculation for the request was clipped to a 32-bit integer. With
the correct stuff->nUnits value the expected request size was
truncated, passing the REQUEST_FIXED_SIZE check.
The server then proceeded with reading at least stuff->nUnits bytes
(depending on stuff->format) from the request and stuffing whatever it
finds into the property. In the process it would also allocate at least
stuff->nUnits bytes, i.e. 4GB.
Discovery 2023-12-13 Entry 2023-12-13 xorg-server
xephyr
xorg-vfbserver
< 21.1.10,1
xorg-nestserver
< 21.1.10,2
xwayland
< 23.2.3,1
xwayland-devel
< 21.0.99.1.582
https://lists.x.org/archives/xorg-announce/2023-December/003435.html
CVE-2023-6377
CVE-2023-6478
|
6cc63bf5-a727-4155-8ec4-68b626475e68 | xorg-server -- Security issue in the X server
The X.org project reports:
Discovery 2023-02-07 Entry 2023-02-08 xorg-server
xephyr
xorg-vfbserver
< 21.1.7,1
xorg-nestserver
< 21.1.7,2
xwayland
< 22.1.8,1
xwayland-devel
< 21.0.99.1.386
https://lists.x.org/archives/xorg-announce/2023-February/003320.html
CVE-2023-0494
|
ab881a74-c016-4e6d-9f7d-68c8e7cedafb | xorg-server -- Multiple Issues
xorg-server developers reports:
In the X.Org X server before 2017-06-19, a user authenticated to
an X Session could crash or execute code in the context of the X
Server by exploiting a stack overflow in the endianness conversion
of X Events.
Uninitialized data in endianness conversion in the XEvent handling
of the X.Org X Server before 2017-06-19 allowed authenticated
malicious users to access potentially privileged data from the X
server.
Discovery 2017-07-06 Entry 2017-10-17 Modified 2018-05-20 xorg-server
<= 1.18.4_6,1
>= 1.19.0,1 le 1.19.3,1
http://www.securityfocus.com/bid/99546
https://bugzilla.suse.com/show_bug.cgi?id=1035283
https://cgit.freedesktop.org/xorg/xserver/commit/?id=215f894965df5fb0bb45b107d84524e700d2073c
https://cgit.freedesktop.org/xorg/xserver/commit/?id=8caed4df36b1f802b4992edcfd282cbeeec35d9d
https://cgit.freedesktop.org/xorg/xserver/commit/?id=ba336b24052122b136486961c82deac76bbde455
http://www.securityfocus.com/bid/99543
https://bugzilla.suse.com/show_bug.cgi?id=1035283
https://cgit.freedesktop.org/xorg/xserver/commit/?id=05442de962d3dc624f79fc1a00eca3ffc5489ced
CVE-2017-10971
CVE-2017-10972
|
fe2b6597-c9a4-11dc-8da8-0008a18a9961 | xorg -- multiple vulnerabilities
Matthieu Herrb of X.Org reports:
Several vulnerabilities have been identified in server code
of the X window system caused by lack of proper input validation
on user controlled data in various parts of the software,
causing various kinds of overflows.
Exploiting these overflows will crash the X server or,
under certain circumstances allow the execution of arbitray
machine code.
When the X server is running with root privileges (which is the
case for the Xorg server and for most kdrive based servers),
these vulnerabilities can thus also be used to raise
privileges.
All these vulnerabilities, to be exploited succesfully, require
either an already established connection to a running X server
(and normally running X servers are only accepting authenticated
connections), or a shell access with a valid user on the machine
where the vulnerable server is installed.
Discovery 2008-01-18 Entry 2008-01-23 xorg-server
< 1.4_4,1
libXfont
< 1.3.1_2,1
CVE-2007-5760
CVE-2007-5958
CVE-2007-6427
CVE-2007-6428
CVE-2007-6429
CVE-2008-0006
http://lists.freedesktop.org/archives/xorg/2008-January/031918.html
http://lists.freedesktop.org/archives/xorg/2008-January/032099.html
http://secunia.com/advisories/28532/
|
9fa7b139-c1e9-409e-bed0-006aadcf5845 | xorg-server -- Multiple security issues in X server extensions
The X.org project reports:
- CVE-2022-46340/ZDI-CAN-19265: X.Org Server XTestSwapFakeInput stack
overflow
The swap handler for the XTestFakeInput request of the XTest extension
may corrupt the stack if GenericEvents with lengths larger than 32 bytes
are sent through a the XTestFakeInput request.
This issue does not affect systems where client and server use the same
byte order.
- CVE-2022-46341/ZDI-CAN-19381: X.Org Server XIPassiveUngrab
out-of-bounds access
The handler for the XIPassiveUngrab request accesses out-of-bounds
memory when invoked with a high keycode or button code.
- CVE-2022-46342/ZDI-CAN-19400: X.Org Server XvdiSelectVideoNotify
use-after-free
The handler for the XvdiSelectVideoNotify request may write to memory
after it has been freed.
- CVE-2022-46343/ZDI-CAN-19404: X.Org Server ScreenSaverSetAttributes
use-after-free
The handler for the ScreenSaverSetAttributes request may write to memory
after it has been freed.
- CVE-2022-46344/ZDI-CAN-19405: X.Org Server XIChangeProperty
out-of-bounds access
The handler for the XIChangeProperty request has a length-validation
issues, resulting in out-of-bounds memory reads and potential
information disclosure.
- CVE-2022-4283/ZDI-CAN-19530: X.Org Server XkbGetKbdByName use-after-free
The XkbCopyNames function left a dangling pointer to freed memory,
resulting in out-of-bounds memory access on subsequent XkbGetKbdByName
requests.
Discovery 2022-12-14 Entry 2023-01-11 xorg-server
xephyr
xorg-vfbserver
< 21.1.5,1
xorg-nestserver
< 21.1.5,2
xwayland
< 22.1.6,1
xwayland-devel
< 21.0.99.1.319
https://lists.x.org/archives/xorg-announce/2022-December/003302.html
CVE-2022-46340
CVE-2022-46341
CVE-2022-46342
CVE-2022-46343
CVE-2022-46344
CVE-2022-4283
|
4f8ffb9c-f388-4fbd-b90f-b3131559d888 | xorg-server -- multiple vulnerabilities
Alan Coopersmith reports:
X.Org thanks Michal Srb of SuSE for finding these issues
and bringing them to our attention, Julien Cristau of
Debian for getting the fixes integrated, and Adam Jackson
of Red Hat for publishing the release.
Discovery 2017-10-04 Entry 2017-10-09 xephyr
< 1.18.4_4,1
xorg-dmx
< 1.18.4_4,1
xorg-nestserver
< 1.19.1_1,2
xorg-server
< 1.18.4_4,1
xorg-vfbserver
< 1.19.1_1,1
xwayland
< 1.19.1_1
https://lists.x.org/archives/xorg-announce/2017-October/002809.html
CVE-2017-13721
CVE-2017-13723
|
7274e0cc-575f-41bc-8619-14a41b3c2ad0 | xorg-server -- multiple vulnerabilities
Adam Jackson reports:
One regression fix since 1.19.4 (mea culpa), and fixes for
CVEs 2017-12176 through 2017-12187.
Discovery 2017-10-12 Entry 2017-10-13 xephyr
< 1.18.4_5,1
xorg-dmx
< 1.18.4_5,1
xorg-nestserver
< 1.19.1_2,2
xorg-server
< 1.18.4_5,1
xorg-vfbserver
< 1.19.1_2,1
xwayland
< 1.19.1_2
https://lists.x.org/archives/xorg-announce/2017-October/002814.html
CVE-2017-12176
CVE-2017-12177
CVE-2017-12178
CVE-2017-12179
CVE-2017-12180
CVE-2017-12181
CVE-2017-12182
CVE-2017-12183
CVE-2017-12184
CVE-2017-12185
CVE-2017-12186
CVE-2017-12187
|
465db5b6-9c6d-11eb-8e8a-bc542f4bd1dd | xorg-server -- Input validation failures in X server XInput extension
X.Org server security reports for release 1.20.11:
- Fix XChangeFeedbackControl() request underflow
.
Discovery 2021-04-13 Entry 2021-04-13 xorg-server
< 1.20.11,1
xwayland
< 1.20.11,1
xwayland-devel
<= 1.20.0.877
https://gitlab.freedesktop.org/xorg/xserver/-/tags/xorg-server-1.20.11
|
9e2fdfc7-e237-4393-9fa5-2d50908c66b3 | xorg-server -- Multiple vulnerabilities
The X.Org project reports:
- ZDI-CAN-22153/CVE-2023-5367: X.Org server: OOB write
in XIChangeDeviceProperty/RRChangeOutputProperty
When prepending values to an existing property an
invalid offset calculation causes the existing values to
be appended at the wrong offset. The resulting memcpy()
would write into memory outside the heap-allocated
array.
- ZDI-CAN-21608/CVE-2023-5380: Use-after-free bug in
DestroyWindow
This vulnerability requires a legacy multi-screen setup
with multiple protocol screens ("Zaphod"). If the pointer
is warped from one screen to the root window of the other
screen, the enter/leave code may retain a reference to the
previous pointer window. Destroying this window leaves
that reference in place, other windows may then trigger a
use-after-free bug when they are destroyed.
Discovery 2023-10-25 Entry 2023-10-25 xorg-server
xephyr
xorg-vfbserver
< 21.1.9,1
xorg-nestserver
< 21.1.9,2
xwayland
< 23.2.2,1
xwayland-devel
< 21.0.99.1.542
https://lists.x.org/archives/xorg-announce/2023-October/003430.html
CVE-2023-5367
CVE-2023-5380
|
7467c611-b490-11ee-b903-001fc69cd6dc | xorg server -- Multiple vulnerabilities
The X.Org project reports:
- CVE-2023-6816: Heap buffer overflow in DeviceFocusEvent
and ProcXIQueryPointer
Both DeviceFocusEvent and the XIQueryPointer reply contain a bit
for each logical button currently down. Buttons can be arbitrarily
mapped to any value up to 255 but the X.Org Server was only
allocating space for the device's number of buttons,
leading to a heap overflow if a bigger value was used.
- CVE-2024-0229: Reattaching to different master device may lead
to out-of-bounds memory access
If a device has both a button class and a key class and
numButtons is zero, we can get an out-of-bounds write due
to event under-allocation in the DeliverStateNotifyEvent
function.
- CVE-2024-21885: Heap buffer overflow in
XISendDeviceHierarchyEvent
The XISendDeviceHierarchyEvent() function allocates space to
store up to MAXDEVICES (256) xXIHierarchyInfo structures in info.
If a device with a given ID was removed and a new device with
the same ID added both in the same operation,
the single device ID will lead to two info structures being
written to info.
Since this case can occur for every device ID at once,
a total of two times MAXDEVICES info structures might be written
to the allocation, leading to a heap buffer overflow.
- CVE-2024-21886: Heap buffer overflow in DisableDevice
The DisableDevice() function is called whenever an enabled device
is disabled and it moves the device from the inputInfo.devices
linked list to the inputInfo.off_devices linked list.
However, its link/unlink operation has an issue during the recursive
call to DisableDevice() due to the prev pointer pointing to a
removed device.
This issue leads to a length mismatch between the total number of
devices and the number of device in the list, leading to a heap
overflow and, possibly, to local privilege escalation.
Discovery 2024-01-16 Entry 2024-01-16 xorg-server
xephyr
xorg-vfbserver
< 21.1.11,1
xorg-nextserver
< 21.1.11,2
xwayland
< 23.2.4
xwayland-devel
< 21.0.99.1.653
CVE-2023-6816
CVE-2024-0229
CVE-2024-21885
CVE-2024-21886
https://lists.x.org/archives/xorg/2024-January/061525.html
|
76c8b690-340b-11eb-a2b7-54e1ad3d6335 | xorg-server -- Multiple input validation failures in X server XKB extension
The X.org project reports:
These issues can lead to privileges elevations for authorized
clients on systems where the X server is running privileged.
Insufficient checks on the lengths of the XkbSetMap request can
lead to out of bounds memory accesses in the X server.
Insufficient checks on input of the XkbSetDeviceInfo request can
lead to a buffer overflow on the head in the X server.
Discovery 2020-12-01 Entry 2020-12-01 xorg-server
< 1.20.9_1,1
xephyr
< 1.20.9_1,1
xorg-vfbserver
< 1.20.9_1,1
xorg-nestserver
< 1.20.9_1,1
xwayland
< 1.20.9_2,1
xorg-dmx
< 1.20.9_1,1
https://lists.x.org/archives/xorg-announce/2020-December/003066.html
CVE-2020-14360
CVE-2020-25712
|