Skip to main content

CWE-305: Authentication Bypass by Primary Weakness

BaseDraft

The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms

Frequently Asked Questions

What is CWE-305: Authentication Bypass by Primary Weakness?+

CWE-305: Authentication Bypass by Primary Weakness is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error.

What are the security consequences of Authentication Bypass by Primary Weakness?+

If exploited, CWE-305 (Authentication Bypass by Primary Weakness) it can compromise Access Control, leading to outcomes such as Bypass Protection Mechanism.

Which programming languages are affected by Authentication Bypass by Primary Weakness?+

CWE-305 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 Primary Weakness?+

MITRE documents real CVEs mapped to CWE-305, including CVE-2002-1374, CVE-2000-0979 and CVE-2001-0088. 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-305 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