CWE-302: Authentication Bypass by Assumed-Immutable Data

BaseIncomplete

The authentication scheme or implementation uses key data elements that are assumed to be immutable, but can be controlled or modified by the attacker.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-302 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-302, Authentication Bypass by Assumed-Immutable Data, 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 Authentication Bypass by Assumed-Immutable Data during Architecture and Design

MITRE associates mitigation with Architecture and Design, Operation, and Implementation; recorded impacts include Bypass Protection Mechanism; the entry maps to CAPEC-10, CAPEC-13, CAPEC-21, and CAPEC-274. Use these source-defined anchors to turn CWE-302 into implementation, review, and verification checks for the affected component.

CWE-302: Authentication Bypass by Assumed-Immutable Data — MITRE CWE

Triage CWE-302 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-302, Authentication Bypass by Assumed-Immutable Data, 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-302

Apply MITRE's full root-cause mapping guidance when using CWE-302, Authentication Bypass by Assumed-Immutable Data. 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-302 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-302, Authentication Bypass by Assumed-Immutable Data. 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-302: Authentication Bypass by Assumed-Immutable Data?+

CWE-302: Authentication Bypass by Assumed-Immutable Data is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The authentication scheme or implementation uses key data elements that are assumed to be immutable, but can be controlled or modified by the attacker.

What are the security consequences of Authentication Bypass by Assumed-Immutable Data?+

If exploited, CWE-302 (Authentication Bypass by Assumed-Immutable Data) it can compromise Access Control, leading to outcomes such as Bypass Protection Mechanism.

How do you prevent or mitigate Authentication Bypass by Assumed-Immutable Data?+

Recommended mitigations for CWE-302 include: Implement proper protection for immutable data (e.g. environment variable, hidden form fields, etc.)

Which programming languages are affected by Authentication Bypass by Assumed-Immutable Data?+

CWE-302 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 Authentication Bypass by Assumed-Immutable Data?+

MITRE documents real CVEs mapped to CWE-302, including CVE-2002-0367, CVE-2004-0261, CVE-2002-1730, CVE-2002-1734 and CVE-2002-2064. 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-302 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.

Learn More

Find Related CVEs

Search for vulnerabilities that exploit CWE-302

CVE vs CWE: What's the Difference?

Understanding vulnerabilities vs weaknesses

Understanding CVSS Scoring

How vulnerability severity is measured

View Full MITRE Entry

Complete technical details and references

Advertisement