Accounts Not Required to Have a Password

Accounts carry the PASSWD_NOTREQD flag, which lets them work with an empty password even where the domain password policy requires one.

SeverityMedium
CVSS 3.14.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N Open in the calculator
CVSS 4.06.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-521: Weak Password Requirements
OWASP Top 10A07:2025 Authentication Failures
MITRE ATT&CKT1078.002 Domain Accounts, T1110.003 Password Spraying
CategorySecurity Misconfiguration

Description

The PASSWD_NOTREQD flag (value 0x0020) in an account's userAccountControl attribute lets the account work with an empty password, even where the domain's password policy requires one. The flag is not shown among the account options in Active Directory Users and Computers, so it often goes unnoticed. It is typically left by provisioning tools, scripts and migrations: an account created through LDAP without an initial password is given the flag, and tools that later enable the account often leave it in place.

The flag does not mean that the account has an empty password, only that it is allowed to. Where a flagged account does have an empty password, anyone who can reach a domain controller can authenticate as that account and gain its access to the domain and its resources, without any prior foothold, and where the password is merely weak, password spraying is likely to find it. What that gives depends on the account: often the access of a standard user, but sometimes that of a service or administrative account created by the same tool. The rating reflects the typical case, in which a flagged account must still be found to have an empty or weak password before it can be used.

Any domain user can list flagged accounts with the LDAP filter (userAccountControl:1.2.840.113556.1.4.803:=32) or Get-ADUser -Filter 'PasswordNotRequired -eq $true'. The weakness is then confirmed by attempting to authenticate to each enabled account with an empty password, for example with NetExec, using a single attempt per account so that no account is locked out.

Remediation

  • Find the tool or process that sets the flag, such as an account creation script, an identity management connector or a migration tool, and correct it so that new accounts are created with a password and without the flag.
  • For each flagged account that is still needed, set a password that meets the policy and then clear the flag. Clearing the flag does not change an existing password, so the reset is what removes an empty one.
  • Disable flagged accounts that are no longer needed.
  • Check for the flag regularly, since provisioning tools can set it again.

For example, to list flagged accounts and, once each has a compliant password, clear the flag:

Get-ADUser -Filter 'PasswordNotRequired -eq $true' -Properties PasswordLastSet | Select-Object SamAccountName, Enabled, PasswordLastSet Get-ADUser -Filter 'PasswordNotRequired -eq $true' | Set-ADAccountControl -PasswordNotRequired $false

Confirm the fix by running the query again, which should return no enabled accounts, and by repeating the empty-password test against the accounts that were flagged.

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 Active Directory Findings

Every Active Directory finding