CWE-521Weak Password Requirements

Description

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

Common consequences

• Access Control→Gain Privileges or Assume Identity
  An attacker could easily guess user passwords and gain access user accounts.

Potential mitigations

• Architecture and Design
  [object Object]
• 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 th

Related CWEs

Recent CVEs classified under this CWE