CWE-308: Use of Single-factor Authentication
Description
The product uses an authentication algorithm that uses a single factor (e.g., a password) in a security context that should require more than one factor.
- Abstraction
- BaseA weakness specific enough to point to detection and prevention methods.
- Likelihood of exploit
- High
- Status
- Draft
Common consequences
- Access Control
Bypass Protection Mechanism
If the secret in a single-factor authentication scheme gets compromised, full authentication is possible.
Potential mitigations
- Architecture and Design
Use multiple independent authentication schemes, which ensures that -- if one of the methods is compromised -- the system itself is still likely safe from compromise. For this reason, if multiple schemes are possible, they should be implemented and required -- especially if they are easy to use.
Related 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-644Use of Captured Hashes (Pass The Hash)
- CAPEC-645Use of Captured Tickets (Pass The Ticket)
- CAPEC-652Use of Known Kerberos Credentials
- CAPEC-653Use of Known Operating System Credentials