Weakness Name | |
---|---|
Insufficiently Protected Credentials The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. |
|
Use of Single-factor Authentication The use of single-factor authentication can lead to unnecessary risk of compromise when compared with the benefits of a dual-factor authentication scheme. |
|
Use of Password System for Primary Authentication The use of password systems as the primary means of authentication may be subject to several flaws or shortcomings, each reducing the effectiveness of the mechanism. |
|
Authentication Bypass by Capture-replay A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes). |
|
Password Aging with Long Expiration The product supports password aging, but the expiration period is too long. |
|
Not Using Password Aging The product does not have a mechanism in place for managing password aging. |
|
Weak Password Requirements The product does not require that users should have strong passwords, which makes it easier for attackers to compromise user accounts. |
Name | Organization | Date | Date Release |
---|---|---|---|
CAPEC Content Team | The MITRE Corporation |
Name | Organization | Date | Comment |
---|---|---|---|
CAPEC Content Team | The MITRE Corporation | Updated Description Summary, Examples-Instances, References, Related_Weaknesses, Typical_Severity | |
CAPEC Content Team | The MITRE Corporation | Updated @Abstraction, Related_Attack_Patterns, Related_Weaknesses, Taxonomy_Mappings | |
CAPEC Content Team | The MITRE Corporation | Updated Taxonomy_Mappings |