CVE Vulnerabilities


Integer Overflow or Wraparound

Published: Oct 10, 2023 | Modified: May 22, 2024
CVSS 3.x
CVSS 2.x

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.


The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.

Affected Software

Name Vendor Start Version End Version
Libx11 * 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 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 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 xenial *

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • If possible, choose a language or compiler that performs automatic bounds checking.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • Use libraries or frameworks that make it easier to handle numbers without unexpected consequences.
  • Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++). [REF-106]
  • Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.
  • Use unsigned integers where possible. This makes it easier to perform validation for integer overflows. When signed integers are required, ensure that the range check includes minimum values as well as maximum values.
  • Understand the programming language’s underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, “not-a-number” calculations, and how the language handles numbers that are too large or too small for its underlying representation. [REF-7]
  • Also be careful to account for 32-bit, 64-bit, and other potential differences that may affect the numeric representation.