Synopsis
The remote Debian host is missing one or more security-related updates.
Description
The remote Debian 11 / 12 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-5603 advisory.
- A flaw was found in X.Org server. 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 particular number of buttons, leading to a heap overflow if a bigger value was used. (CVE-2023-6816)
- A flaw was found in the X.Org server. The GLX PBuffer code does not call the XACE hook when creating the buffer, leaving it unlabeled. When the client issues another request to access that resource (as with a GetGeometry) or when it creates another resource that needs to access that buffer, such as a GC, the XSELINUX code will try to use an object that was never labeled and crash because the SID is NULL.
(CVE-2024-0408)
- A flaw was found in the X.Org server. The cursor code in both Xephyr and Xwayland uses the wrong type of private at creation. It uses the cursor bits type with the cursor as private, and when initiating the cursor, that overwrites the XSELINUX context. (CVE-2024-0409)
- The X.Org project reports: 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. 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. 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. 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.
(CVE-2024-0229, CVE-2024-21885, CVE-2024-21886)
Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.
Solution
Upgrade the xdmx packages.
Plugin Details
File Name: debian_DSA-5603.nasl
Agent: unix
Supported Sensors: Agentless Assessment, Frictionless Assessment Agent, Nessus Agent, Nessus
Risk Information
Vector: CVSS2#AV:N/AC:L/Au:N/C:C/I:C/A:C
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Temporal Vector: CVSS:3.0/E:U/RL:O/RC:C
Vulnerability Information
CPE: p-cpe:/a:debian:debian_linux:xnest, p-cpe:/a:debian:debian_linux:xserver-xorg-core, cpe:/o:debian:debian_linux:11.0, p-cpe:/a:debian:debian_linux:xserver-xorg-core-udeb, p-cpe:/a:debian:debian_linux:xdmx, p-cpe:/a:debian:debian_linux:xwayland, p-cpe:/a:debian:debian_linux:xdmx-tools, p-cpe:/a:debian:debian_linux:xserver-common, p-cpe:/a:debian:debian_linux:xvfb, p-cpe:/a:debian:debian_linux:xserver-xephyr, p-cpe:/a:debian:debian_linux:xserver-xorg-dev, p-cpe:/a:debian:debian_linux:xorg-server-source, cpe:/o:debian:debian_linux:12.0, p-cpe:/a:debian:debian_linux:xserver-xorg-legacy
Required KB Items: Host/local_checks_enabled, Host/Debian/release, Host/Debian/dpkg-l
Exploit Ease: No known exploits are available
Patch Publication Date: 1/23/2024
Vulnerability Publication Date: 1/16/2024