FreeRDP
FreeRDP: Heap-buffer-overflow write in TS Gateway RPC fragment receive due to uncapped bind_ack max_xmit_frag
FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.27.0, FreeRDP clients using TS Gateway accept a server-controlled max_xmit_frag value in libfreerdp/core/gateway/rpc_bind.c without bounding it to the 4088-byte ReceiveFragment allocation. A malicious gateway can advertise 65535 and then send a response fragment of the same length, causing rpc_channel_read in libfreerdp/core/gateway/rpc.c to write up to 65535 bytes into the smaller ReceiveFragment buffer. This can crash the client and may permit code execution through attacker-controlled heap corruption. This issue is fixed in version 3.27.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 3.27.0
Fixed in 3.27.0
Mitigation
Upgrade FreeRDP to 3.27.0 or later.
References
- Vendor advisory github.com/FreeRDP/FreeRDP/security/advisories…
- Patch github.com/FreeRDP/FreeRDP/pull/12873
- Patch github.com/FreeRDP/FreeRDP/commit/a863ef1cf1cd…
1 more
- Release notes github.com/FreeRDP/FreeRDP/releases/tag/3.27.0
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.