COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.
Implementation
Not enforcing the password policy stated in a products design can allow users to create passwords that do not provide the necessary level of protection.
key server application does not require strong passwords
Potential Mitigations
Phase: 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:
执行最小和最大长度
Restrictions against password reuse
限制使用通用密码
Restrictions against using contextual string in the password (e.g., user id, app name)
Depending on the threat model, the password policy may include several additional attributes.
需要混合字符集的复杂密码(alpha,数字,特殊,混合案例)
Increasing the range of characters makes the password harder to crack and may be appropriate for systems relying on single factor authentication.
Consider a second authentication factor beyond the password, which prevents the password from being a single point of failure. SeeCWE-308了解更多信息。
Phase: Implementation
Consider implementing a password complexity meter to inform users when a chosen password meets the required attributes.
Memberships
This MemberOf Relationships table shows additional CWE Categories and Views that reference this weakness as a member. This information is often useful in understanding where a weakness fits within the context of external information sources.
自然
Type
ID
姓名
MemberOf
Category - a CWE entry that contains a set of other entries that share a common characteristic.