# CVE-2024-22211: FreeRDP integer Overflow leading to Heap Overflow

> A malicious server can trigger a heap overflow in FreeRDP clients via integer overflow, potentially leading to code execution or crashes.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:L`)
- **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:** 19 Jan 2024
- **Updated:** 3 Nov 2025
- **Also known as:** CLEANSTART-2024-SZ47948, DEBIAN-CVE-2024-22211, GHSA-rjhp-44rv-7v59, OESA-2024-1108, SUSE-SU-2024:0648-1, SUSE-SU-2024:0649-1, UBUNTU-CVE-2024-22211

## What is CVE-2024-22211?

CVE-2024-22211 is a low-severity vulnerability in Freerdp Freerdp, published on 19 Jan 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

FreeRDP is a set of free and open source remote desktop protocol library and clients. In affected versions an integer overflow in `freerdp_bitmap_planar_context_reset` leads to heap-buffer overflow. This affects FreeRDP based clients. FreeRDP based server implementations and proxy are not affected. A malicious server could prepare a `RDPGFX_RESET_GRAPHICS_PDU` to allocate too small buffers, possibly triggering later out of bound read/write. Data extraction over network is not possible, the buffers are used to display an image. This issue has been addressed in version 2.11.5 and 3.2.0. Users are advised to upgrade. there are no know workarounds for this vulnerability.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2024-22211?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `freerdp` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 2.4.0-150400.3.26.1 |
| `freerdp` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 2.1.2-12.41.1 |
| `freerdp` | SUSE:Linux Enterprise Workstation Extension 12 SP5 | All versions | 2.1.2-12.41.1 |
| `freerdp` | SUSE:Linux Enterprise Workstation Extension 15 SP5 | All versions | 2.4.0-150400.3.26.1 |
| `freerdp` | openSUSE:Leap 15.5 | All versions | 2.4.0-150400.3.26.1 |

Products: Freerdp Freerdp.

## How do I fix CVE-2024-22211?

Upgrade to a fixed version.

## Is CVE-2024-22211 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22211 exists.

## Other vulnerabilities in Freerdp Freerdp

- [CVE-2021-37594](https://insights.sbomify.com/CVE-2021-37594/): Other in n/a (critical 9.8)
- [CVE-2021-37595](https://insights.sbomify.com/CVE-2021-37595/): Other in n/a (critical 9.8)
- [CVE-2026-67305](https://insights.sbomify.com/CVE-2026-67305/): FreeRDP Windows Client before 3.29.0 Heap Buffer Overflow via Cliprdr (critical 9.4)
- [CVE-2026-66402](https://insights.sbomify.com/CVE-2026-66402/): FreeRDP before 3.29.0 TLS Certificate Identity Validation Bypass (critical 9.3)
- [CVE-2026-67289](https://insights.sbomify.com/CVE-2026-67289/): FreeRDP before 3.29.0 HTTP Proxy Request Injection via Redirection (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22211 and fix it if it is affected.

What it is: CVE-2024-22211 is a low-severity vulnerability in Freerdp Freerdp, published on 19 Jan 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22211 exists.

Affected product: Freerdp Freerdp. 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-2024-22211/ (Markdown: https://insights.sbomify.com/CVE-2024-22211/index.md)
```

## Sources

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

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