Read the docs

FreeRDP server commits memory based on client-declared DVC length

Priority MEDIUM 44CWE-400Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · High
Fix status
Fixed

Attack profile from CVSS 3.1 · GHSA-5cgr-vmp8-fmvj. Fix status from GitHub. Impact type from CWE-400.

Summary

FreeRDP versions from 2.0.0 through 3.31.1 are affected in server applications that open a dynamic virtual channel (DVC). The DVC receive path trusts the client's declared 32-bit message length (CWE-770) and zero-fills the full stream before the message body arrives. A remote client with an accepted session can send a tiny header declaring a 256 MiB message, which makes the server commit that memory and causes resource exhaustion.

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

Description from the GitHub advisory

## Summary Once a FreeRDP server application has opened a DVC, `wts_read_drdynvc_data_first` trusts the client's 32-bit declared message length and grows the DVC receive stream to that total before the remaining body arrives. `Stream_EnsureCapacity` zeroes the added range, so this is committed resident memory rather than lazy virtual address space. In a live stock client-to-server replay, a seven-byte 256 MiB declaration increased AddressSanitizer server RSS by 264,380 KiB; a seven-byte 64 KiB control increased it by 2,304 KiB. Both receivers remained alive. ## Prerequisites The attacker can establish a session accepted under the embedding server's authentication policy. The client and server negotiate `drdynvc`, and the receiver application opens a DVC that reaches the succeeded-open state. The tested path used an application-created `AUDIO_INPUT` channel. The stock sample server required a disclosed application-level VCM initialization scaffold; the core parser and allocator were unmodified. ## Non-claims The test did not terminate the server and does not demonstrate a successful 4 GiB allocation, memory corruption, data disclosure, privilege escalation, or remote code execution. ## Remediation No upstream fix was found in the assessed master snapshot. Recommended remediation is a trusted per-message maximum before allocation, cleanup on rejection, and per-session and process-wide DVC memory accounting.

Why it matters now

Fix Fixed FreeRDP (c): 3.32.0

SSVC decision points

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

Affected products

VendorProductAffected versionsFixed inStatusSource
—FreeRDP (c)>= 2.0.0, <= 3.31.13.32.0Patch availableGHSA-5cgr-vmp8-fmvj
  • FreeRDP (c) Vendor— Affected >= 2.0.0, <= 3.31.1 Fixed in 3.32.0 Patch available GHSA-5cgr-vmp8-fmvj

Remediation

Upgrade FreeRDP to version 3.32.0, the listed fixed version.

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

  • Fix · GHSA-5cgr-vmp8-fmvj FreeRDP (c) Fixed in 3.32.0 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-5cgr-vmp8-fmvj

References

Sources

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