COMMON WEAKNESS ENUMERATIONDraft

CWE-308

Use of Single-factor Authentication

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

Base

Structure

Simple

Likelihood of Exploit

High

Understand the problem

What is the problem?

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.

Root cause

How and when does the problem arise?

Lifecycle phase

Architecture and Design

COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.

Risk

What does successful exploitation lead to?

Bypass Protection Mechanism

Affected security scopes: Access Control

If the secret in a single-factor authentication scheme gets compromised, full authentication is possible.

Defence

How is it prevented and fixed?

Architecture and Design

Architecture and design approach

Detail
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.

MITRE diagram

Weakness relationships and flow

CWE-308 MITRE diagramı
CWE-308: Common Weakness Enumeration Entry CWE-308 · DayBreach Sözlük · DayBreach