Weak Domain Password Policy

The domain password policy allows short passwords or does not lock accounts after repeated failures, making passwords easier to guess and to crack.

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&CKT1110.003 Password Spraying, T1110.001 Password Guessing, T1110.002 Password Cracking
CategorySecurity Misconfiguration

Description

The password and account lockout settings in the Default Domain Policy apply to every domain account, unless a fine-grained password policy overrides them for particular users or groups; password settings in Group Policy objects linked to organisational units affect only local accounts. The finding arises when these settings do not require passwords strong enough to resist guessing and cracking. Common examples are a minimum length of eight characters or fewer (the default is seven), no account lockout (the default threshold of 0 never locks accounts), a threshold so high that it does not slow guessing, and storage of passwords with reversible encryption.

Such a policy makes password guessing and cracking more likely to succeed. Without lockout, an attacker can try many passwords against each account through any service that authenticates against the domain; even with lockout, password spraying (a few common passwords tried against every account) succeeds where short passwords are allowed. Complexity rules on their own do little: users meet them with predictable patterns, such as a season and a year followed by a symbol, and frequent forced changes encourage the same patterns. Short passwords that meet the rules can also be cracked quickly offline from captured material such as Kerberoasting output, NTLMv2 challenge responses and dumped NT hashes. Each recovered password gives the attacker that user's access, and may belong to a privileged or service account. The actual exposure depends on the passwords users choose and on whether multi-factor authentication protects remote access.

The domain policy can be read by any domain user, for example with Get-ADDefaultDomainPasswordPolicy, net accounts /domain or NetExec's --pass-pol option, and fine-grained policies with Get-ADFineGrainedPasswordPolicy where the account in use can read them. Where in scope, an audit of extracted password hashes shows the resulting password quality directly.

Remediation

  • Raise the minimum password length, for example to at least 14 characters for user accounts, and encourage passphrases such as three random words. Use fine-grained password policies (password settings objects) to set longer minimums for administrators and service accounts, and where a minimum beyond what the domain policy setting accepts is wanted.
  • Set an account lockout threshold, for example between 5 and 10 failed attempts, with a lockout duration and counter reset time of at least 15 minutes, balancing protection against guessing with the risk of deliberate lockouts.
  • Block common and breached passwords, as current NCSC and NIST guidance recommends, for example with Microsoft Entra Password Protection for Active Directory Domain Services or another password filter on the domain controllers.
  • Disable Store passwords using reversible encryption in the policy and on individual accounts, and reset the passwords of any accounts that had it.
  • Once length and blocklist checks are in place, consider dropping frequent forced expiry for user accounts, which the same guidance advises against, and require a change whenever compromise is suspected.
  • Require multi-factor authentication for remote and administrative access, which limits the value of a guessed password.

Existing passwords only have to meet a new policy when they are next changed. Confirm the fix by reading the effective policies again, and track adoption through password age or a later password audit.

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