Weak RDP Encryption Configuration
The Remote Desktop service accepts the legacy RDP security layer or a low encryption level, letting an attacker in the network path intercept sessions and capture credentials.
| Severity | Medium |
| CVSS 3.1 | 5.4 CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N Open in the calculator |
| CVSS 4.0 | 5.9 CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-757: Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade') |
| OWASP Top 10 | A04:2025 Cryptographic Failures |
| MITRE ATT&CK | T1557 Adversary-in-the-Middle, T1040 Network Sniffing |
| Category | Cryptographic Failures |
Description
The host's Remote Desktop service allows connections that use the legacy RDP security layer, also called Standard RDP Security or native RDP encryption, instead of TLS, or accepts a low encryption level. The legacy layer encrypts traffic with RC4 (Triple DES at the FIPS Compliant level) and does not authenticate the server in a way the client can verify. At the Low encryption level only data sent from the client to the server is encrypted, so traffic from the server to the client, including everything displayed on screen, is not encrypted at all; at the Client Compatible level the strength is whatever the client supports.
The behaviour is controlled by two settings: the security layer (RDP, Negotiate or SSL) and the client connection encryption level (Low, Client Compatible, High or FIPS Compliant). Negotiate allows the legacy layer whenever a client asks for it, which an attacker who intercepts the connection can arrange by altering the client's request.
An attacker able to intercept traffic between a user and the host, for example by ARP spoofing on the same network segment, can therefore place themselves in the middle of a Remote Desktop connection that uses the legacy layer, or force one to use it, and so capture the credentials the user types at the sign-in screen and observe or alter the session. Freely available tools automate this. The attack needs a position in the network path and a user who connects while it is in place, which in most cases limits it to the internal network.
The Nmap rdp-enum-encryption script lists the security layers the server accepts and, for the legacy layer, the encryption levels. Scanners report the issue as a Remote Desktop man-in-the-middle weakness, or as an encryption level of medium or low.
Remediation
Require TLS and strong encryption for every Remote Desktop connection:
- In Group Policy, under Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Security, set Require use of specific security layer for remote (RDP) connections to SSL, set Set client connection encryption level to High Level, and enable Require user authentication for remote connections by using Network Level Authentication.
- On individual hosts, the first two settings are the
SecurityLayer(2 for SSL) andMinEncryptionLevel(3 for High) DWORD values underHKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp. - Replace the default self-signed Remote Desktop certificate with one issued by an internal certificate authority that clients trust, for example with the Server authentication certificate template policy in the same location, so that clients can verify the server.
- Configure clients to refuse servers that cannot be authenticated, with the Configure server authentication for client policy under Remote Desktop Connection Client set to Do not connect if authentication fails.
Confirm the fix with the Nmap rdp-enum-encryption script, which should no longer report the native RDP layer as accepted.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.