# CVE-2023-42822: Unchecked access to font glyph info in xrdp

> An attacker can trigger an out-of-bounds read in xrdp, potentially leading to information disclosure or privilege escalation in privileged processes.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 27 Sep 2023
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-42822, GHSA-2hjx-rm4f-r9hw, MGASA-2023-0334, SUSE-SU-2023:4577-1, UBUNTU-CVE-2023-42822

## What is CVE-2023-42822?

CVE-2023-42822 is a medium-severity memory corruption vulnerability in Fedoraproject Fedora, published on 27 Sep 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

xrdp is an open source remote desktop protocol server. Access to the font glyphs in xrdp_painter.c is not bounds-checked . Since some of this data is controllable by the user, this can result in an out-of-bounds read within the xrdp executable. The vulnerability allows an out-of-bounds read within a potentially privileged process. On non-Debian platforms, xrdp tends to run as root. Potentially an out-of-bounds write can follow the out-of-bounds read. There is no denial-of-service impact, providing xrdp is running in forking mode. This issue has been addressed in release 0.9.23.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xrdp` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 0.9.13.1-150200.4.27.1 |
| `xrdp` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 0.9.13.1-150200.4.27.1 |
| `xrdp` | openSUSE:Leap 15.4 | All versions | 0.9.13.1-150200.4.27.1 |
| `xrdp` | openSUSE:Leap 15.5 | All versions | 0.9.13.1-150200.4.27.1 |

Products: Fedoraproject Fedora, Neutrinolabs Xrdp.

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

Upgrade to a fixed version.

## Is CVE-2023-42822 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-42822 is a medium-severity memory corruption vulnerability in Fedoraproject Fedora, published on 27 Sep 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-42822 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. 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-42822/ (Markdown: https://insights.sbomify.com/CVE-2023-42822/index.md)
```

## Sources

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

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