CWE-263: Password Aging with Long Expiration
Description
The product supports password aging, but the expiration period is too long.
Password aging (or password rotation) is a policy that forces users to change their passwords after a defined time period passes, such as every 30 or 90 days. A long expiration provides more time for attackers to conduct password cracking before users are forced to change to a new password. Note that while password aging was once considered an important security feature, it has since fallen out of favor by many, because it is not as effective against modern threats compared to other mechanisms such as slow hashes. In addition, forcing frequent changes can unintentionally encourage users to select less-secure passwords. However, password aging is still in use due to factors such as compliance requirements, e.g., Payment Card Industry Data Security Standard (PCI DSS).
- Abstraction
- BaseA weakness specific enough to point to detection and prevention methods.
- Likelihood of exploit
- Low
- Status
- Draft
Common consequences
- Access Control
Gain Privileges or Assume Identity
As passwords age, the probability that they are compromised grows.
Potential mitigations
- 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...
- Architecture and Design
Ensure that password aging is limited so that there is a defined maximum age for passwords. Note that if the expiration window is too short, it can cause users to generate poor or predictable passwords.
- Architecture and Design
Ensure that the user is notified several times leading up to the password expiration.
- Architecture and Design
Create mechanisms to prevent users from reusing passwords or creating similar passwords.
- ImplementationEffectiveness: Discouraged Common Practice
Developers might disable clipboard paste operations into password fields as a way to discourage users from pasting a password into a clipboard. However, this might encourage users to choose less-secure passwords that are easier to type, and it can reduce the usability of password managers.
Related weaknesses
Parent weaknesses
CAPEC attack patterns that exploit it
- CAPEC-16Dictionary-based Password Attack
- CAPEC-49Password Brute Forcing
- CAPEC-55Rainbow Table Password Cracking
- CAPEC-70Try Common or Default Usernames and Passwords
- CAPEC-509Kerberoasting
- CAPEC-555Remote Services with Stolen Credentials
- CAPEC-560Use of Known Domain Credentials
- CAPEC-561Windows Admin Shares with Stolen Credentials
- CAPEC-565Password Spraying
- CAPEC-600Credential Stuffing
- CAPEC-652Use of Known Kerberos Credentials
- CAPEC-653Use of Known Operating System Credentials