CVE Vulnerabilities

CVE-2024-21885

Heap-based Buffer Overflow

Published: Feb 28, 2024 | Modified: Sep 16, 2024
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
7.8 IMPORTANT
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM

A flaw was found in X.Org server. In the XISendDeviceHierarchyEvent function, it is possible to exceed the allocated array length when certain new device IDs are added to the xXIHierarchyInfo struct. This can trigger a heap buffer overflow condition, which may lead to an application crash or remote code execution in SSH X11 forwarding environments.

Weakness

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Affected Software

Name Vendor Start Version End Version
Red Hat Enterprise Linux 7 RedHat xorg-x11-server-0:1.20.4-27.el7_9 *
Red Hat Enterprise Linux 7 RedHat tigervnc-0:1.8.0-31.el7_9 *
Red Hat Enterprise Linux 8 RedHat tigervnc-0:1.13.1-2.el8_9.7 *
Red Hat Enterprise Linux 8 RedHat xorg-x11-server-0:1.20.11-22.el8 *
Red Hat Enterprise Linux 8 RedHat xorg-x11-server-Xwayland-0:21.1.3-15.el8 *
Red Hat Enterprise Linux 8.2 Advanced Update Support RedHat tigervnc-0:1.9.0-15.el8_2.9 *
Red Hat Enterprise Linux 8.2 Telecommunications Update Service RedHat tigervnc-0:1.9.0-15.el8_2.9 *
Red Hat Enterprise Linux 8.2 Update Services for SAP Solutions RedHat tigervnc-0:1.9.0-15.el8_2.9 *
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support RedHat tigervnc-0:1.11.0-8.el8_4.8 *
Red Hat Enterprise Linux 8.4 Telecommunications Update Service RedHat tigervnc-0:1.11.0-8.el8_4.8 *
Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions RedHat tigervnc-0:1.11.0-8.el8_4.8 *
Red Hat Enterprise Linux 8.6 Extended Update Support RedHat tigervnc-0:1.12.0-6.el8_6.9 *
Red Hat Enterprise Linux 8.8 Extended Update Support RedHat tigervnc-0:1.12.0-15.el8_8.7 *
Red Hat Enterprise Linux 9 RedHat tigervnc-0:1.13.1-3.el9_3.6 *
Red Hat Enterprise Linux 9 RedHat xorg-x11-server-0:1.20.11-24.el9 *
Red Hat Enterprise Linux 9 RedHat xorg-x11-server-Xwayland-0:22.1.9-5.el9 *
Red Hat Enterprise Linux 9.0 Extended Update Support RedHat tigervnc-0:1.11.0-22.el9_0.8 *
Red Hat Enterprise Linux 9.2 Extended Update Support RedHat tigervnc-0:1.12.0-14.el9_2.5 *
Xorg Ubuntu bionic *
Xorg Ubuntu trusty *
Xorg Ubuntu xenial *
Xorg-server Ubuntu bionic *
Xorg-server Ubuntu devel *
Xorg-server Ubuntu esm-infra/bionic *
Xorg-server Ubuntu esm-infra/xenial *
Xorg-server Ubuntu focal *
Xorg-server Ubuntu jammy *
Xorg-server Ubuntu lunar *
Xorg-server Ubuntu mantic *
Xorg-server Ubuntu noble *
Xorg-server Ubuntu oracular *
Xorg-server Ubuntu trusty *
Xorg-server Ubuntu trusty/esm *
Xorg-server Ubuntu upstream *
Xorg-server Ubuntu xenial *
Xorg-server-hwe-16.04 Ubuntu xenial *
Xorg-server-hwe-18.04 Ubuntu bionic *
Xorg-server-lts-utopic Ubuntu trusty *
Xorg-server-lts-vivid Ubuntu trusty *
Xorg-server-lts-wily Ubuntu trusty *
Xorg-server-lts-xenial Ubuntu trusty *
Xwayland Ubuntu devel *
Xwayland Ubuntu jammy *
Xwayland Ubuntu lunar *
Xwayland Ubuntu mantic *
Xwayland Ubuntu noble *
Xwayland Ubuntu oracular *

Potential Mitigations

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
  • D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
  • Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
  • Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
  • For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].

References