Read the docs

FreeRDP proxy accepts untrusted target certificates with no verifier

Priority MEDIUM 45CWE-295Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
High
Impact type
Spoofing
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · GHSA-pjxv-5j98-cqx4. Fix status from GitHub. Impact type from CWE-295.

Summary

FreeRDP's proxy manages certificates for its outbound target connection through an external callback, which accepts the presented target certificate when no proxy module vetoes it. A network-positioned attacker can impersonate the configured RDP target with a self-signed, wrong-hostname certificate if they receive or intercept the proxy's outbound connection and a user starts a proxied session. In a live proxy replay, the default no-module configuration sent 395 post-TLS RDP bytes, while a required rejecting module sent none. The weakness is CWE-295, Improper Certificate Validation.

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

Description from the GitHub advisory

## Summary The FreeRDP proxy enables external certificate management for its outbound target connection. Its certificate callback accepts the target certificate when no proxy module vetoes it. A network-positioned attacker can therefore impersonate the configured RDP target with a self-signed, wrong-hostname certificate. In a live proxy replay, the default no-module configuration sent 395 post-TLS RDP bytes; a required rejecting module sent zero. ## Prerequisites The deployment uses the FreeRDP proxy with TLS to its target and has no module that validates and rejects the presented target certificate. The attacker must receive or intercept the proxy's outbound connection, and a user must initiate a proxied session. ## Remediation No upstream fix was found in current master. Recommended remediation is normal chain and hostname verification for the outbound target, or fail-closed external management that requires an explicit verifier decision.

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-pjxv-5j98-cqx4
  • FreeRDP (c) Vendor— Affected >= 2.0.0, <= 3.31.1 Fixed in 3.32.0 Patch available GHSA-pjxv-5j98-cqx4

Remediation

Upgrade FreeRDP to 3.32.0 or later. No upstream fix was found in current master at the time of writing. Until a fix is available, enable normal chain and hostname verification for the outbound target, or configure fail-closed external management that requires an explicit verifier decision.

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

  • Fix · GHSA-pjxv-5j98-cqx4 FreeRDP (c) Fixed in 3.32.0 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-pjxv-5j98-cqx4

References

Sources

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