Read the docs

Use-after-free in FreeRDP async update 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 through 3.28.0 has client-side heap use-after-free flaws in the async update message proxy for RAIL window and notify icon orders when AsyncUpdate is enabled. The proxy copies structures with nested buffers that the parser frees after the callback returns, so queued messages use stale pointers. A malicious or compromised RDP server sending crafted update orders can trigger them.

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 related client-side heap-use-after-free issues in the async update message proxy for RAIL `WINDOW_STATE_ORDER` and `NOTIFY_ICON_STATE_ORDER`. When `AsyncUpdate` is enabled, the message proxy shallow-copies structures that contain nested parser-owned pointers. The parser frees those nested buffers after callback return, while the queued async message later dispatches stale pointers to the real callback. I reproduced both paths on supported release 3.28.0 with AddressSanitizer. Description: `WINDOW_STATE_ORDER` path: - `libfreerdp/core/message.c:1259`: `CopyMemory(lParam, windowState, sizeof(WINDOW_STATE_ORDER));` - `libfreerdp/core/message.c:1290`: same shallow copy for `WindowUpdate` - `libfreerdp/core/window.c:866`: parser fills local `WINDOW_STATE_ORDER windowState` - `libfreerdp/core/window.c:873`: callback is invoked; with `AsyncUpdate`, this is the message-proxy callback - `libfreerdp/core/window.c:881`: parser frees nested buffers after callback return - `libfreerdp/core/message.c:2407`: queued `WindowCreate` later dispatches stale nested pointers Nested parser-owned pointers include `titleInfo.string`, `windowRects`, `visibilityRects`, and `OverlayDescription.string`. `NOTIFY_ICON_STATE_ORDER` path: - `libfreerdp/core/message.c:1453`: `CopyMemory(lParam, notifyIconState, sizeof(NOTIFY_ICON_STATE_ORDER));` - `libfreerdp/core/message.c:1485`: same shallow copy for `NotifyIconUpdate` - `libfreerdp/core/window.c:981`: parser fills local `NOTIFY_ICON_STATE_ORDER notify_icon_state` - `libfreerdp/core/window.c:989`: callback is invoked; with `AsyncUpdate`, this is the message-proxy callback - `libfreerdp/core/window.c:997`: parser frees nested buffers via `update_notify_icon_state_order_free()` - `libfreerdp/core/message.c:2431`: queued `NotifyIconCreate` later dispatches stale nested pointers Nested parser-owned pointers include `toolTip.string`, `infoTip.text.string`, `infoTip.title.string`, `icon.bitsColor`, `icon.bitsMask`, and `icon.colorTable`. Reproduction evidence: Both reproducers feed real Window Alternate Secondary Orders through the production parser path. Artifacts in my local package: - Window harness: `docker_repro/freerdp_window_order_message_proxy_uaf_harness.c` - Window ASan log: `docker_repro/window_order_message_proxy_uaf_asan_run.txt` - NotifyIcon harness: `docker_repro/freerdp_notify_icon_message_proxy_uaf_harness.c` - NotifyIcon ASan log: `docker_repro/notify_icon_message_proxy_uaf_asan_run.txt` Key Window ASan result: ```text ERROR: AddressSanitizer: heap-use-after-free READ of size 2 #0 sink_window_create docker_repro/freerdp_window_order_message_proxy_uaf_harness.c:61 #1 update_message_process_window_update_class freerdp_3_28_0_src/libfreerdp/core/message.c:2407 freed by: #1 update_free_window_state docker_repro/freerdp_window_order_message_proxy_uaf_harness.c:26 #2 update_recv_window_info_order freerdp_3_28_0_src/libfreerdp/core/window.c:881 allocated by: #1 rail_read_unicode_string freerdp_3_28_0_src/libfreerdp/core/window.c:62 #2 update_read_window_state_order freerdp_3_28_0_src/libfreerdp/core/window.c:284 ``` Key NotifyIcon ASan result: ```text ERROR: AddressSanitizer: heap-use-after-free READ of size 2 #0 sink_notify_icon_create docker_repro/freerdp_notify_icon_message_proxy_uaf_harness.c:70 #1 update_message_process_window_update_class freerdp_3_28_0_src/libfreerdp/core/message.c:2431 freed by: #1 update_notify_icon_state_order_free freerdp_3_28_0_src/libfreerdp/core/window.c:890 #2 update_recv_notification_icon_info_order freerdp_3_28_0_src/libfreerdp/core/window.c:997 allocated by: #1 rail_read_unicode_string freerdp_3_28_0_src/libfreerdp/core/window.c:62 #2 update_read_notification_icon_state_order freerdp_3_28_0_src/libfreerdp/core/window.c:910 ``` Impact: The confirmed impact is client-side heap-use-after-free in queued async RAIL window/notification icon dispatch. The minimal release harness for these two paths reads freed heap content and continues, so I am not claiming a demonstrated release-build crash or RCE for these two variants. The security risk is memory corruption or client crash depending on allocator state and callback behavior. Suggested classification: - CWE-416: Use After Free - Suggested severity: Moderate - Affected version: 3.28.0; latest public master was also checked and the vulnerable shallow-copy patterns 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-33gg-h66j-3697
  • FreeRDP (c/c++) Vendor— Affected <=3.28.0 Fixed in 3.29.0 Patch available GHSA-33gg-h66j-3697

Remediation

Upgrade FreeRDP to version 3.29.0, which fixes the flaw.

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

  • Fix · GHSA-33gg-h66j-3697 FreeRDP (c/c++) Fixed in 3.29.0 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-33gg-h66j-3697

References

Sources

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