Weak or Guessable Passwords in Use
Accounts use passwords that are common, short or follow predictable patterns, so an attacker can sign in by trying a few likely values.
| Severity | High |
| CVSS 3.1 | 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N Open in the calculator |
| CVSS 4.0 | 8.8 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-521: Weak Password Requirements |
| OWASP Top 10 | A07:2025 Authentication Failures |
| MITRE ATT&CK | T1110.001 Password Guessing, T1110.003 Password Spraying, T1078 Valid Accounts |
| Category | Security Misconfiguration |
Description
Accounts on the application or service were found to use passwords that are easily guessed: common passwords such as Password1 or Welcome123, a season or month followed by the year, the company or product name with a number, the username repeated, short numeric values, or passwords that appear in public breach collections. Complexity rules do not prevent them, because predictable patterns satisfy most composition requirements. Service, shared and administrative accounts are frequent offenders, because their passwords are set by hand, rarely changed and often exempt from the policy applied to ordinary users.
Such passwords fall within the first few attempts of a dictionary or password spraying attack, and spraying a few common passwords across many accounts makes success likely wherever weak passwords are in use, while leaving little trace when each account receives only one or two attempts. An attacker who guesses a password can sign in as that user and act with all of the user's access: reading and changing their data, using any function available to them and, where the account is privileged or its password is reused on other systems, extending access further. The impact is greatest for administrative, service and remote access accounts, and is much reduced where multi-factor authentication is enforced, because the password alone is then not enough to sign in.
The finding is usually confirmed by trying a small number of likely passwords against each account at the login interface while staying below any lockout threshold (password spraying), by cracking password hashes recovered elsewhere in the test, or by reviewing credentials found in configuration files and scripts. Tools such as Hydra, Burp Suite Intruder and dedicated spraying tools are commonly used.
Remediation
- Require the affected users to change their passwords at once, starting with privileged, service and remote access accounts, and review the accounts' recent activity for signs of misuse.
- Screen every new password against a blocklist of common, expected and breached values, including the organisation's own name, product names and keyboard and seasonal patterns. NIST SP 800-63B requires this check, and services such as the Pwned Passwords range API allow it without sending the password or its full hash.
- Enforce a minimum length rather than composition rules: NIST SP 800-63B-4 sets 15 characters for passwords used as the only factor and 8 characters for passwords used with a second factor, and recommends allowing at least 64 characters so that passphrases can be used.
- Enforce multi-factor authentication, which removes most of the value of a guessed password.
- Replace passwords on service accounts with long random values held in a secrets manager, or with managed identities or keys where the platform supports them.
- Rate limit login attempts and monitor for password spraying, where many accounts each receive a few attempts.
Confirm the fix by repeating the guessing attempts against the affected accounts, and by attempting to set a known weak password through the normal password change function.
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.