Vulnerabilities
Misconfiguration
Runtime Security
Compliance
CVE Vulnerabilities

CVE-2023-43787

Heap-based Buffer Overflow

Published: Oct 10, 2023 | Modified: Nov 21, 2024
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
7.8 MODERATE
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2023-43787
CWEhttps://cwe.mitre.org/data/definitions/122.html

A vulnerability was found in libX11 due to an integer overflow within the XCreateImage() function. This flaw allows a local user to trigger an integer overflow and execute arbitrary code with elevated privileges.

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
Libx11 X.org * 1.8.7 (excluding)
Red Hat Enterprise Linux 8 RedHat libX11-0:1.6.8-8.el8 *
Red Hat Enterprise Linux 9 RedHat libX11-0:1.7.0-9.el9 *
Libx11 Ubuntu bionic *
Libx11 Ubuntu devel *
Libx11 Ubuntu esm-infra/bionic *
Libx11 Ubuntu esm-infra/xenial *
Libx11 Ubuntu focal *
Libx11 Ubuntu jammy *
Libx11 Ubuntu lunar *
Libx11 Ubuntu mantic *
Libx11 Ubuntu noble *
Libx11 Ubuntu oracular *
Libx11 Ubuntu trusty *
Libx11 Ubuntu trusty/esm *
Libx11 Ubuntu upstream *
Libx11 Ubuntu xenial *
Libxpm Ubuntu bionic *
Libxpm Ubuntu devel *
Libxpm Ubuntu esm-infra/bionic *
Libxpm Ubuntu esm-infra/xenial *
Libxpm Ubuntu focal *
Libxpm Ubuntu jammy *
Libxpm Ubuntu lunar *
Libxpm Ubuntu mantic *
Libxpm Ubuntu noble *
Libxpm Ubuntu oracular *
Libxpm Ubuntu trusty *
Libxpm Ubuntu trusty/esm *
Libxpm Ubuntu upstream *
Libxpm Ubuntu xenial *
Motif Ubuntu bionic *
Motif Ubuntu lunar *
Motif Ubuntu mantic *
Motif Ubuntu trusty *
Motif Ubuntu trusty/esm *
Motif Ubuntu xenial *

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

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2025 Aqua Security Software Ltd.   Privacy Policy | Terms of Use