CWEweakness
CWE-262 Not Using Password Aging
Low
Official page ↗
- Abstraction
- Base
- Structure
- Simple
- Status
- Draft
- Likelihood of exploit
- Low
- Languages
- Not Language-Specific
- CWE version
- 5.0
Description
The product does not have a mechanism in place for managing password aging.
Extended description
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).
Common consequences
• Access Control: Gain Privileges or Assume Identity — As passwords age, the probability that they are compromised grows.
Potential mitigations
• [Architecture and Design] As part of a product's design, require users to change their passwords regularly and avoid reusing previous passwords.
• [Implementation] 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 [REF-1294].
Related
Attack pattern · CAPEC (12)
- CAPEC-16 Dictionary-based Password Attack attack pattern
- CAPEC-49 Password Brute Forcing attack pattern
- CAPEC-509 Kerberoasting attack pattern
- CAPEC-55 Rainbow Table Password Cracking attack pattern
- CAPEC-555 Remote Services with Stolen Credentials attack pattern
- CAPEC-560 Use of Known Domain Credentials attack pattern
- CAPEC-561 Windows Admin Shares with Stolen Credentials attack pattern
- CAPEC-565 Password Spraying attack pattern
- CAPEC-600 Credential Stuffing attack pattern
- CAPEC-652 Use of Known Kerberos Credentials attack pattern
- CAPEC-653 Use of Known Operating System Credentials attack pattern
- CAPEC-70 Try Common or Default Usernames and Passwords attack pattern
Child of · CWE (2)
Peer of · CWE (2)
Referenced by CAPEC · weakness (12)
- CAPEC-16 Dictionary-based Password Attack attack pattern
- CAPEC-49 Password Brute Forcing attack pattern
- CAPEC-509 Kerberoasting attack pattern
- CAPEC-55 Rainbow Table Password Cracking attack pattern
- CAPEC-555 Remote Services with Stolen Credentials attack pattern
- CAPEC-560 Use of Known Domain Credentials attack pattern
- CAPEC-561 Windows Admin Shares with Stolen Credentials attack pattern
- CAPEC-565 Password Spraying attack pattern
- CAPEC-600 Credential Stuffing attack pattern
- CAPEC-652 Use of Known Kerberos Credentials attack pattern
- CAPEC-653 Use of Known Operating System Credentials attack pattern
- CAPEC-70 Try Common or Default Usernames and Passwords attack pattern
Referenced by CVE · weakness (6)
- CVE-2026-50101 Naxclow devices use a server-side, per-device relay credential that never rotates and is re-issued to the device on each boot. vulnerability
- CVE-2025-60010 A password aging vulnerability in the RADIUS client of Juniper Networks Junos OS and Junos OS Evolved allows an authenticated,… vulnerability
- CVE-2025-58435 Open OnDemand is an open-source HPC portal. vulnerability
- CVE-2023-1555 An issue has been discovered in GitLab affecting all versions starting from 15.2 before 16.1.5, all versions starting from 16.2 before… vulnerability
- CVE-2023-2022 An issue has been discovered in GitLab CE/EE affecting all versions starting before 16.0.8, all versions starting from 16.1 before 16.1.3,… vulnerability
- CVE-2022-22767 Specific BD Pyxis™ products were installed with default credentials and may presently still operate with these credentials. vulnerability
Referenced by CWE · has member (1)
- CWE-884 CWE Cross-section view