Read the docs

Use-after-free in FreeRDP WindowIcon async message proxy

Priority LOW 38Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub.

Summary

FreeRDP up to and including 3.28.0 contains a use-after-free in the async update message proxy for WINDOW_ICON_ORDER, where the queued window icon data is freed by the parser while still referenced. When AsyncUpdate is enabled, a malicious or compromised RDP server can send a crafted RAIL window alternate secondary order that causes the client to dispatch a stale pointer. The reporter reproduced it on release 3.28.0 with AddressSanitizer and a release-build client crash.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

Reporter / credit: Bin Luo, University of Electronic Science and Technology of China (UESTC), [email protected] Target: - Repository: FreeRDP/FreeRDP - Supported release reproduced: 3.28.0 - Reproduction commit: 5370fb26fbf034ecd11d3026b6ad639b5fff493f - Condition: AsyncUpdate enabled, for example xfreerdp `/async-update` - Threat model: malicious or compromised RDP server sending crafted update orders to a client Summary: FreeRDP 3.28.0 contains a client-side heap-use-after-free in the async update message proxy for `WINDOW_ICON_ORDER`. When `AsyncUpdate` is enabled, a malicious or compromised RDP server can send a crafted RAIL Window Alternate Secondary Order with `WINDOW_ORDER_ICON`. The parser-owned `ICON_INFO` is freed after the parser callback returns, but the queued async message later dispatches a stale pointer to the real `WindowIcon` callback. I reproduced this on supported release 3.28.0 with AddressSanitizer and also reproduced a release-build client crash in the local harness. Description: In `libfreerdp/core/message.c`, `update_message_WindowIcon()` tries to deep-copy a `WINDOW_ICON_ORDER` for asynchronous dispatch: ```c lParam = (WINDOW_ICON_ORDER*)calloc(1, sizeof(WINDOW_ICON_ORDER)); lParam->iconInfo = calloc(1, sizeof(ICON_INFO)); CopyMemory(lParam, windowIcon, sizeof(WINDOW_ICON_ORDER)); ``` The final `CopyMemory()` shallow-copies the whole source order over the destination and overwrites the newly allocated `lParam->iconInfo` with the parser-owned `windowIcon->iconInfo` pointer. Later assignments then operate through the parser-owned `ICON_INFO`. After the callback returns, `libfreerdp/core/window.c` frees `window_icon.iconInfo`, but the queued async message still retains that pointer and later dispatches it from `update_message_process_window_update_class()`. Relevant code locations on 3.28.0: - `libfreerdp/core/message.c:1313`: allocate queued `WINDOW_ICON_ORDER` - `libfreerdp/core/message.c:1318`: allocate queued `ICON_INFO` - `libfreerdp/core/message.c:1323`: shallow copy overwrites `lParam->iconInfo` - `libfreerdp/core/message.c:2418`: queued `WindowIcon` dispatch uses the stale `ICON_INFO*` - `libfreerdp/core/window.c:498`: parser allocates `window_icon.iconInfo` - `libfreerdp/core/window.c:833`: production parser reads `WindowIcon` - `libfreerdp/core/window.c:842-843`: parser frees `window_icon.iconInfo` after callback return Reproduction evidence: The reproducer feeds a real Window Alternate Secondary Order through: `update_recv_altsec_window_order()` -> `update_read_window_icon_order()` -> `update_message_WindowIcon()`. Artifacts in my local package: - Harness: `docker_repro/freerdp_window_icon_message_proxy_uaf_harness.c` - ASan log: `docker_repro/window_icon_message_proxy_uaf_asan_run.txt` - Release log: `docker_repro/window_icon_message_proxy_uaf_release_run.txt` Key ASan result: ```text ERROR: AddressSanitizer: heap-use-after-free READ of size 4 #0 sink_window_icon docker_repro/freerdp_window_icon_message_proxy_uaf_harness.c:55 #1 update_message_process_window_update_class freerdp_3_28_0_src/libfreerdp/core/message.c:2418 freed by: #1 update_recv_window_info_order freerdp_3_28_0_src/libfreerdp/core/window.c:843 allocated by: #1 update_read_window_icon_order freerdp_3_28_0_src/libfreerdp/core/window.c:498 ``` Release-build result: ```text Segmentation fault (core dumped) EXIT_CODE=139 ``` Impact: The confirmed impact is a client-side heap-use-after-free and release-build crash when async update processing is enabled. I am not claiming demonstrated remote code execution. The risk is memory corruption in a client process controlled by server-supplied RAIL update data. Suggested classification: - CWE-416: Use After Free - Suggested severity: Moderate - Affected version: 3.28.0; latest public master was also checked and the vulnerable copy pattern still appeared present at the time of testing.

Why it matters now

Fix Fixed FreeRDP (c/c++): 3.29.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—FreeRDP (c/c++)<=3.28.03.29.0Patch availableGHSA-34hq-hwjw-q8v3
  • FreeRDP (c/c++) Vendor— Affected <=3.28.0 Fixed in 3.29.0 Patch available GHSA-34hq-hwjw-q8v3

Remediation

Upgrade FreeRDP to version 3.29.0 or later, which fixes the flaw.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-34hq-hwjw-q8v3 FreeRDP (c/c++) Fixed in 3.29.0 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-34hq-hwjw-q8v3

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences