FreeRDP accepts client-only certificates as TLS server certificates
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 accepts a server TLS certificate that is valid only for client authentication, because certificate verification falls back to client and any purpose checks after the server purpose check fails. An attacker who holds a certificate from a CA the client trusts, with a hostname matching the target, can present it as the RDP server certificate and bypass the extended key usage policy. The flaw is an improper certificate purpose validation, not memory corruption, and no exploitation is reported.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
## Summary FreeRDP's client-side TLS certificate verification can accept a peer certificate that is valid only for client authentication as an RDP server certificate. This is a certificate-purpose / EKU policy bypass in the server TLS authentication path. Reporter / credit: Bin Luo, UESTC ## Confirmed versions - Current master HEAD tested: f3b4347105114fe7453828736bea069999af319f - Tree version: 3.28.0-49-gf3b434710 - Supported release checked: 3.28.0 - Relevant files unchanged between 3.28.0 and current master for this path: libfreerdp/crypto/x509_utils.c, libfreerdp/crypto/certificate.c, libfreerdp/crypto/tls.c ## Affected code path - libfreerdp/crypto/tls.c: tls_verify_certificate() - libfreerdp/crypto/certificate.c: freerdp_certificate_verify() - libfreerdp/crypto/x509_utils.c: x509_utils_verify() ## Root cause x509_utils_verify() tries multiple OpenSSL certificate purposes: X509_PURPOSE_SSL_SERVER X509_PURPOSE_SSL_CLIENT X509_PURPOSE_ANY In the client-side server-certificate verification path, if server-purpose verification fails because the certificate is unsuitable for server authentication, the code continues to try client-purpose and any-purpose verification. As a result, a certificate that is otherwise trusted and matches the hostname, but is only valid for clientAuth, can be accepted as the RDP server certificate. ## Reproduction evidence I reproduced this with a local Docker/ASan harness using FreeRDP's production TLS client path. The harness creates: - a trusted local test CA; - a leaf certificate for eku.example.com; - subjectAltName=DNS:eku.example.com; - a critical EKU containing only clientAuth, not serverAuth; - an isolated FreeRDP certificate store containing the test CA; - an in-memory TLS server/client BIO pair using FreeRDP's production freerdp_tls_connect_ex() and freerdp_tls_handshake() path. OpenSSL comparison for the same certificate: OpenSSL verify -purpose sslserver: fails with unsuitable certificate purpose OpenSSL verify -purpose sslclient: OK OpenSSL hostname check for eku.example.com: matches FreeRDP result for the same certificate: Certificate verification warning: unsuitable certificate purpose (26) case host=eku.example.com freerdp_tls_result=0 server_done=1 openssl_x509_check_host=1 freerdp_tls_result=0 is TLS_HANDSHAKE_SUCCESS. ## Impact This is not memory corruption and I am not claiming RCE. The security impact is improper TLS server certificate purpose validation. In environments that rely on EKU separation between client and server certificates, FreeRDP may accept a certificate that standard server-purpose verification rejects. A realistic exploit requires the FreeRDP client to trust the issuing CA or chain, and the certificate hostname to match the target. The issue is specifically that a clientAuth-only certificate is accepted for server authentication. ## Suggested fix For server certificate verification, do not fall back to X509_PURPOSE_SSL_CLIENT or X509_PURPOSE_ANY after X509_PURPOSE_SSL_SERVER fails. The client-side server-certificate path should require serverAuth-compatible purpose semantics. I can provide the Docker harness and generated test certificate material if useful.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | FreeRDP (c/c++) | <= 3.28.0 | 3.29.0 | Patch available | GHSA-89c6-jjrw-96h4 |
- FreeRDP (c/c++) Vendor— Affected <= 3.28.0 Fixed in 3.29.0 Patch available GHSA-89c6-jjrw-96h4
Remediation
Upgrade FreeRDP to version 3.29.0 or later, where the fix is listed. The sources list no fixed version for other FreeRDP branches.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-89c6-jjrw-96h4 FreeRDP (c/c++) Fixed in 3.29.0 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-89c6-jjrw-96h4
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences