RDP Network Level Authentication Not Enforced

The Remote Desktop service does not require Network Level Authentication, so anyone who can reach it is given a Windows sign-in session before proving who they are.

SeverityMedium
CVSS 3.15.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Open in the calculator
CVSS 4.06.9 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-306: Missing Authentication for Critical Function
OWASP Top 10A07:2025 Authentication Failures
MITRE ATT&CKT1021.001 Remote Desktop Protocol, T1210 Exploitation of Remote Services
CategorySecurity Misconfiguration

Description

The host's Remote Desktop service accepts connections without Network Level Authentication (NLA). With NLA, the client must authenticate through CredSSP before the server creates a session; without it, the server creates a session and shows the Windows sign-in screen to anyone who connects, and the user authenticates inside that session. NLA has been available since Windows Vista and Windows Server 2008 and is selected by default when Remote Desktop is enabled on current releases, so it is usually found turned off for compatibility with old clients or third-party tools, or so that users with expired passwords can change them at sign-in.

Without NLA, anyone who can reach the service reaches code that runs before authentication, including session creation and the sign-in process. This widens the attack surface for pre-authentication vulnerabilities in Remote Desktop Services: Microsoft named NLA as a partial mitigation for BlueKeep (CVE-2019-0708) because it forces an attacker to authenticate first. Unauthenticated connections also consume server resources, which can be used to tie up sessions, and the sign-in screen can reveal the domain name and user names, as it may display the last user to sign in. Password guessing is possible with or without NLA, so the main loss is the barrier in front of pre-authentication flaws.

The security layers a server accepts can be listed without credentials with the Nmap rdp-enum-encryption script: if it reports that native RDP or SSL connections succeed, NLA is not enforced. Connecting with a client and being shown the sign-in screen also confirms it. Scanners report it as Terminal Services or Remote Desktop not using Network Level Authentication only.

Remediation

Require NLA for every Remote Desktop connection:

  • In Group Policy, enable Require user authentication for remote connections by using Network Level Authentication under Computer Configuration, Administrative Templates, Windows Components, Remote Desktop Services, Remote Desktop Session Host, Security.
  • On individual hosts, select Allow connections only from computers running Remote Desktop with Network Level Authentication in the Remote Desktop settings, or set the UserAuthentication DWORD value to 1 under HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp.
  • Update or replace clients and tools that cannot use NLA, and give users another way to change expired passwords, such as a self-service password reset service, so that the setting does not need to be relaxed again.

Where NLA cannot be enforced at once on a host, restrict Remote Desktop access to it to management networks. Confirm the fix with the Nmap rdp-enum-encryption script, which should show only CredSSP (NLA) connections succeeding, and by checking that a client is asked for credentials before any sign-in screen appears.

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 trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Network Services Findings

Every Network Services finding