CWE-308: Use of Single-factor Authentication

Code Examples & CVEs

Demonstrative Examples

In both of these examples, a user is logged in if their given password matches a stored password:

This code relies exclusively on a password mechanism (CWE-309) using only one factor of authentication (CWE-308). If an attacker can steal or guess a user's password, they are given full access to their account. Note this code also uses SHA-1, which is a weak hash (CWE-328). It also does not use a salt (CWE-759).

BadC

unsigned char *check_passwd(char *plaintext) {ctext = simple_digest("sha1",plaintext,strlen(plaintext), ... );                         //Login if hash matches stored hash                         if (equal(ctext, secret_password())) {login_user();}}

In both of these examples, a user is logged in if their given password matches a stored password:

BadJava

String plainText = new String(plainTextIn);MessageDigest encer = MessageDigest.getInstance("SHA");encer.update(plainTextIn);byte[] digest = password.digest();                      //Login if hash matches stored hash                      if (equal(digest,secret_password())) {login_user();}

Observed CVE Examples (1)

CVE-2022-35248

Chat application skips validation when Central Authentication Service (CAS) is enabled, effectively removing the second factor from two-factor authentication

View Details

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-308 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-308, Use of Single-factor Authentication, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Use of Single-factor Authentication during Architecture and Design

MITRE associates mitigation with Architecture and Design; recorded impacts include Bypass Protection Mechanism; the entry maps to CAPEC-16, CAPEC-49, CAPEC-509, and CAPEC-55. Use these source-defined anchors to turn CWE-308 into implementation, review, and verification checks for the affected component.

CWE-308: Use of Single-factor Authentication — MITRE CWE

Triage CWE-308 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-308, Use of Single-factor Authentication, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-308

Apply MITRE's full root-cause mapping guidance when using CWE-308, Use of Single-factor Authentication. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-308 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-308, Use of Single-factor Authentication. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-308: Use of Single-factor Authentication?+

CWE-308: Use of Single-factor Authentication is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Use of Single-factor Authentication?+

If exploited, CWE-308 (Use of Single-factor Authentication) it can compromise Access Control, leading to outcomes such as Bypass Protection Mechanism.

How do you prevent or mitigate Use of Single-factor Authentication?+

Recommended mitigations for CWE-308 include: 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.

Which programming languages are affected by Use of Single-factor Authentication?+

CWE-308 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Use of Single-factor Authentication?+

MITRE documents real CVEs mapped to CWE-308, including CVE-2022-35248. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-308 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-308: Use of Single-factor Authentication

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods