# CVE-2023-5367: Xorg-x11-server: out-of-bounds write in xichangedeviceproperty/rrchangeoutputproperty

> An out-of-bounds write in the Xorg X11 server allows attackers to escalate privileges or cause a denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Oct 2023
- **Updated:** 23 Jun 2026
- **Also known as:** AZL-31720, AZL-44724, BELL-CVE-2023-5367, DEBIAN-CVE-2023-5367, GHSA-q38f-wwqq-rr3v, RHSA-2023:6802, RHSA-2023:6808, RHSA-2023:7373, RHSA-2023:7388, RHSA-2023:7405, RHSA-2023:7436, RHSA-2023:7526, RHSA-2023:7533, RHSA-2024:0128, UBUNTU-CVE-2023-5367

## What is CVE-2023-5367?

CVE-2023-5367 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 25 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A out-of-bounds write flaw was found in the xorg-x11-server. This issue occurs due to an incorrect calculation of a buffer offset when copying data stored in the heap in the XIChangeDeviceProperty function in Xi/xiproperty.c and in RRChangeOutputProperty function in randr/rrproperty.c, allowing for possible escalation of privileges or denial of service.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2023-5367?

It affects 12 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xorg-x11-server` | Red Hat:enterprise_linux:7::client | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xdmx` | Red Hat:enterprise_linux:7::client | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xephyr` | Red Hat:enterprise_linux:7::client | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xnest` | Red Hat:enterprise_linux:7::client | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xorg` | Red Hat:enterprise_linux:7::client | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xvfb` | Red Hat:enterprise_linux:7::client | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xwayland` | Red Hat:enterprise_linux:7::client | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-common` | Red Hat:enterprise_linux:7::client | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-source` | Red Hat:enterprise_linux:7::client | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xdmx` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xephyr` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xnest` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xorg` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xvfb` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xwayland` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-common` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-source` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server` | Red Hat:enterprise_linux:7::server | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xdmx` | Red Hat:enterprise_linux:7::server | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xephyr` | Red Hat:enterprise_linux:7::server | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xnest` | Red Hat:enterprise_linux:7::server | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xorg` | Red Hat:enterprise_linux:7::server | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xvfb` | Red Hat:enterprise_linux:7::server | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xwayland` | Red Hat:enterprise_linux:7::server | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-common` | Red Hat:enterprise_linux:7::server | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-source` | Red Hat:enterprise_linux:7::server | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xdmx` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xephyr` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xnest` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xorg` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xvfb` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.20.4-24.el7_9 |
| `xorg-x11-server-Xwayland` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.20.4-24.el7_9 |

Products: Debian Debian Linux, Fedoraproject Fedora, Redhat Enterprise Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux for Ibm Z Systems, Redhat Enterprise Linux for Power Big Endian, Redhat Enterprise Linux for Power Little Endian, Redhat Enterprise Linux for Scientific Computing, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation, X.org X Server, X.org Xwayland.

## How do I fix CVE-2023-5367?

Apply the vendor's patch.

## Is CVE-2023-5367 being exploited?

There is no known exploitation of CVE-2023-5367 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5367 and fix it if it is affected.

What it is: CVE-2023-5367 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 25 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-5367 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-5367/ (Markdown: https://insights.sbomify.com/CVE-2023-5367/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-5367
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-5367
- OSV: https://osv.dev/vulnerability/CVE-2023-5367

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-5367/
Summaries are generated and may contain mistakes; the official description above is the record.