Base weaknessCWE Catalog

CWE-521: Weak Password Requirements

The product does not require that users should have strong passwords.

How it's found

Weak Password Requirements is typically found by tracing untrusted input from where it enters the system to the point where it is used without the check or neutralization this weakness describes, combining manual code review with dynamic testing.

Consequences

Gain Privileges or Assume Identity: An attacker could easily guess user passwords and gain access user accounts.

Mitigations

Architecture and Design: A product's design should require adherance to an appropriate password policy. Specific password requirements depend strongly on contextual factors, but it is recommended to contain the following attributes: Depending on the threat model, the password policy may include several additional attributes. See NIST 800-63B [REF-1053] for further information on password requirements.Enforcement of a minimum and maximum length Restrictions against password reuse Restrictions against using common passwords Restrictions against using contextual string in the password (e.g., user id, app name) Increasing the range of characters makes the password harder to crack and may be appropriate for systems relying on single factor authentication. Unfortunately, a complex password may be difficult to memorize, encouraging a user to select a short password or to incorrectly manage the password (write it down). Another disadvantage of this approach is that it often does not result in a significant increases in overal password complexity due to people's predictable usage of various symbols.Complex passwords requiring mixed character sets (alpha, numeric, special, mixed case) Increasing the number of characters makes the password harder to crack and may be appropriate for systems relying on single factor authentication. A disadvantage of this approach is that selecting a good passphrase is not easy and poor passwords can still be generated. Some prompting may be needed to encourage long un-predictable passwords.Large Minimum Length (encouraging passphrases instead of passwords) Generating a password for the user can help make sure that length and complexity requirements are met, and can result in secure passwords being used. A disadvantage of this approach is that the resulting password or passpharse may be too difficult to memorize, encouraging them to be written down.Randomly Chosen Secrets
Architecture and Design: Consider a second authentication factor beyond the password, which prevents the password from being a single point of failure. See CWE-308 for further information.
Implementation: Consider implementing a password complexity meter to inform users when a chosen password meets the required attributes.
Implementation: Previously, "password expiration" was widely advocated as a defense-in-depth approach to minimize the risk of weak passwords, and it has become a common practice. Password expiration requires a password to be changed within a fixed time window (such as every 90 days). However, this approach has significant limitations in the current threat landscape, and its utility has been reduced in light of the adoption of related protection mechanisms (such as password complexity and computational effort), along with the recognition that regular password changes often caused users to generate more predictable passwords. As a result, this is now a Discouraged Common Practice [REF-1488] [REF-1489], especially as the sole factor in protecting passwords. It is still strongly encouraged to force password changes in case of evidence of compromise, but this is not the same as a forced "expiration" on an arbitrary time frame.

Where this fits in a TurboPentest engagement

This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.

Frequently asked questions

What is CWE-521?

The product does not require that users should have strong passwords.

How do you find Weak Password Requirements?

What is the impact of CWE-521?

Gain Privileges or Assume Identity: An attacker could easily guess user passwords and gain access user accounts.

Does TurboPentest test for Weak Password Requirements?

This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.

Related CWEs

Written and reviewed by

Michel Chamberland - Founder & CEO, IntegSec

CISSP, OSCP, OSCE, CEH, GIAC, CCSK · 20+ years in offensive security

Michel has spent 20+ years on offensive security teams including IBM X-Force Red and Trustwave SpiderLabs, leading penetration tests, red team engagements, and breach response for Fortune 500 customers. He is the founder of IntegSec and the architect of TurboPentest.

Find these issues before an attacker does

TurboPentest runs an agentic AI pentest against your target and reports findings with proof, from $99 per target.

Start a pentest

CWE-521: Weak Password Requirements

The product does not require that users should have strong passwords.

How it's found

Consequences

Gain Privileges or Assume Identity: An attacker could easily guess user passwords and gain access user accounts.

Mitigations

Architecture and Design: A product's design should require adherance to an appropriate password policy. Specific password requirements depend strongly on contextual factors, but it is recommended to contain the following attributes: Depending on the threat model, the password policy may include several additional attributes. See NIST 800-63B [REF-1053] for further information on password requirements.Enforcement of a minimum and maximum length Restrictions against password reuse Restrictions against using common passwords Restrictions against using contextual string in the password (e.g., user id, app name) Increasing the range of characters makes the password harder to crack and may be appropriate for systems relying on single factor authentication. Unfortunately, a complex password may be difficult to memorize, encouraging a user to select a short password or to incorrectly manage the password (write it down). Another disadvantage of this approach is that it often does not result in a significant increases in overal password complexity due to people's predictable usage of various symbols.Complex passwords requiring mixed character sets (alpha, numeric, special, mixed case) Increasing the number of characters makes the password harder to crack and may be appropriate for systems relying on single factor authentication. A disadvantage of this approach is that selecting a good passphrase is not easy and poor passwords can still be generated. Some prompting may be needed to encourage long un-predictable passwords.Large Minimum Length (encouraging passphrases instead of passwords) Generating a password for the user can help make sure that length and complexity requirements are met, and can result in secure passwords being used. A disadvantage of this approach is that the resulting password or passpharse may be too difficult to memorize, encouraging them to be written down.Randomly Chosen Secrets
Architecture and Design: Consider a second authentication factor beyond the password, which prevents the password from being a single point of failure. See CWE-308 for further information.
Implementation: Consider implementing a password complexity meter to inform users when a chosen password meets the required attributes.
Implementation: Previously, "password expiration" was widely advocated as a defense-in-depth approach to minimize the risk of weak passwords, and it has become a common practice. Password expiration requires a password to be changed within a fixed time window (such as every 90 days). However, this approach has significant limitations in the current threat landscape, and its utility has been reduced in light of the adoption of related protection mechanisms (such as password complexity and computational effort), along with the recognition that regular password changes often caused users to generate more predictable passwords. As a result, this is now a Discouraged Common Practice [REF-1488] [REF-1489], especially as the sole factor in protecting passwords. It is still strongly encouraged to force password changes in case of evidence of compromise, but this is not the same as a forced "expiration" on an arbitrary time frame.

Where this fits in a TurboPentest engagement

This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.

Frequently asked questions

What is CWE-521?

The product does not require that users should have strong passwords.

How do you find Weak Password Requirements?

What is the impact of CWE-521?

Gain Privileges or Assume Identity: An attacker could easily guess user passwords and gain access user accounts.

Does TurboPentest test for Weak Password Requirements?

This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.

Written and reviewed by

Michel Chamberland - Founder & CEO, IntegSec

CISSP, OSCP, OSCE, CEH, GIAC, CCSK · 20+ years in offensive security

Find these issues before an attacker does

TurboPentest runs an agentic AI pentest against your target and reports findings with proof, from $99 per target.

Start a pentest