Weakness (CWE)
CWE-262: Not Using Password Aging
The product does not have a mechanism in place for managing password aging.
More detail
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).
How to prevent it (2 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].
Source: MITRE CWE-262
2 results · Clear filters · Feed
-
High 8.1
Naxclow IoT Platform Not using password aging
Naxclow devices use a server-side, per-device relay credential that never rotates and is re-issued to the device on each boot. Because this credential remains valid indefinitely and cannot be reset or revoked by the legitimate owner, any party that obtains it…
-
High 8.8
BD Pyxis™ Products – Default Credentials
Specific BD Pyxis™ products were installed with default credentials and may presently still operate with these credentials. There may be scenarios where BD Pyxis™ products are installed with the same default local operating system credentials or domain-joined…