FreeRDP
FreeRDPHeap-buffer-overflow write in TS Gateway RPC RESPONSE reassembly due to alloc_hint capacity mismatch
FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to 3.27.0, rpc_client_recv_fragment in libfreerdp/core/gateway/rpc_client.c ensures the response reassembly stream capacity using only the server-declared alloc_hint rather than the actual StubLength about to be written. A malicious TS Gateway can send a PTYPE_RESPONSE with a small alloc_hint and a much larger frag_length, causing Stream_Write to copy attacker-controlled stub data beyond the 4096-byte pdu->s buffer. This can crash the client and may permit code execution through 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/9f2da52c2341…
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.