CVE Vulnerabilities

CVE-2022-46344

Out-of-bounds Read

Published: Dec 14, 2022 | Modified: Dec 13, 2023
CVSS 3.x
8.8
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
8.8 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM

A vulnerability was found in X.Org. This security flaw occurs because the handler for the XIChangeProperty request has a length-validation issues, resulting in out-of-bounds memory reads and potential information disclosure. This issue can lead to local privileges elevation on systems where the X server is running privileged and remote code execution for ssh X forwarding sessions.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name Vendor Start Version End Version
X_server X.org 1.20.4 (including) 1.20.4 (including)
Red Hat Enterprise Linux 7 RedHat tigervnc-0:1.8.0-23.el7_9 *
Red Hat Enterprise Linux 7 RedHat xorg-x11-server-0:1.20.4-21.el7_9 *
Red Hat Enterprise Linux 8 RedHat xorg-x11-server-Xwayland-0:21.1.3-10.el8 *
Red Hat Enterprise Linux 8 RedHat xorg-x11-server-0:1.20.11-15.el8 *
Red Hat Enterprise Linux 8 RedHat tigervnc-0:1.12.0-15.el8_8 *
Red Hat Enterprise Linux 9 RedHat xorg-x11-server-0:1.20.11-17.el9 *
Red Hat Enterprise Linux 9 RedHat xorg-x11-server-Xwayland-0:21.1.3-7.el9 *
Red Hat Enterprise Linux 9 RedHat tigervnc-0:1.12.0-13.el9_2 *
Xorg-server Ubuntu bionic *
Xorg-server Ubuntu devel *
Xorg-server Ubuntu esm-infra/xenial *
Xorg-server Ubuntu focal *
Xorg-server Ubuntu jammy *
Xorg-server Ubuntu kinetic *
Xorg-server Ubuntu lunar *
Xorg-server Ubuntu trusty *
Xorg-server Ubuntu trusty/esm *
Xorg-server Ubuntu xenial *
Xorg-server-hwe-16.04 Ubuntu esm-infra/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 kinetic *
Xwayland Ubuntu lunar *

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

References