Security Resilience

CWE · MITRE source

CWE-306Missing Authentication for Critical Function

Abstraction: Base · CVEs in our corpus: 3,542

The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Last updated: 16 October 2026 00:29 UTC

Cumulative inbound coverage

How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.

Collective: full · 6 mapping(s) from 3 framework(s): STIG rhel 8 2 (full) · STIG rhel 7 2 (mostly) · STIG oracle linux 8 2 (partial)

See the full cumulative-coverage rollup →

OWASP Top 10 for Web (2025)

This weakness contributes to A07:2025 Authentication Failures.

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • IA-1 Policy and Procedures
  • IA-10 Adaptive Authentication
  • IA-11 Re-authentication
  • IA-13 Identity Providers and Authorization Servers
Detect
Catch it (CSF Detect / Respond)

—

Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.2.3
  • V6.4.4
  • V10.4.16
  • V12.1.3

NIST 800-53 r5 controls PROPOSED for this weakness (43)AI-assisted

These are model PROPOSALS, not graded mappings. They come from controls_to_cwe_proposals, which carries no grade field at all; across the CWE pages 1,540 of 1,722 such associations (89%) have never been graded by anything. The heading said “address” until 2026-09-29, which asserted a relationship the data does not carry. Graded cross-walks are on the framework map, not here.

Showing the 15 most specific. Generic controls that address many weakness types are collapsed below.

Control Title Family Why it addresses this CWE
IA-2Identification and Authentication (Organizational Users)IAgraded full Mandates authentication for organizational users and their associated processes, eliminating missing authentication for critical functions.
IA-8Identification and Authentication (Non-organizational Users)IAgraded full Requires authentication for non-organizational users, preventing access to critical functions without proper identification and authentication.
IA-9Service Identification and AuthenticationIAgraded full Mandates authentication prior to establishing communications with services, preventing missing authentication for this critical function.
AC-14Permitted Actions Without Identification or AuthenticationACgraded mostly Requiring identification and rationale for actions allowed without authentication ensures critical functions are not left unprotected by forcing review of authentication requirements.
SA-14Criticality AnalysisSAExplicit identification of critical functions enables organizations to ensure authentication is applied exactly where it is most needed, preventing missing authentication for those functions.
SA-16Developer-provided TrainingSATraining emphasizes enabling and properly using authentication for critical functions, reducing missing authentication exposures.
SA-17Developer Security and Privacy Architecture and DesignSADemands complete description of required security functionality, making omission of authentication for critical functions far less likely.
SC-14Public Access ProtectionsSCRequires authentication gates on critical functions that must remain unavailable to anonymous public users.
SC-15Collaborative Computing Devices and ApplicationsSCTreats remote activation of surveillance-capable devices as a critical function that must be disabled or authenticated.
SC-19Voice Over Internet ProtocolSCRequiring authorization before VoIP deployment prevents critical VoIP functions (registration, call setup) from lacking authentication.
AC-11Device LockACRequires established identification and authentication to unlock, mitigating missing authentication for continued system access.
AC-19Access Control for Mobile DevicesACAuthorizing mobile device connections to organizational systems ensures authentication is performed for this critical access function.
PE-10Emergency ShutoffPEThe shutoff is a critical function, and the control ensures it cannot be activated without proper (physical) authentication.
PE-3Physical Access ControlPERequires verification of individual access authorizations before granting facility entry, addressing missing authentication for critical physical access.
PE-7Visitor ControlPEImplements authentication steps (ID checks, sign-in, escort verification) for physical access to critical functions or locations.
Show 28 more broadly-applicable controls
IA-1Policy and ProceduresIAThe policy mandates identification and authentication for critical functions, making missing authentication less likely.
IA-10Adaptive AuthenticationIAMandates additional authentication for access under defined conditions, ensuring critical or high-risk functions are not left without authentication.
IA-11Re-authenticationIARe-authentication enforces fresh credential validation for critical functions or operations as defined by the organization parameter.
IA-13Identity Providers and Authorization ServersIAIdentity providers mandate authentication for functions that would otherwise lack it.
IA-3Device Identification and AuthenticationIARequires authentication of devices prior to connection, preventing exploitation of missing authentication for critical network functions.
IA-7Cryptographic Module AuthenticationIAMandates authentication for the critical function of accessing or using a cryptographic module.
SA-5System DocumentationSASecure configuration documentation explicitly addresses enabling authentication for critical functions, reducing missing authentication exposures.
SA-8Security and Privacy Engineering PrinciplesSAComplete-mediation principle requires authentication for critical functions.
SA-9External System ServicesSAMandating that external services employ specified authentication controls and ongoing compliance monitoring makes missing authentication for critical functions harder to overlook or exploit.
SC-26DecoysSCDecoy implementations of critical functions without authentication lure and record attackers probing for missing auth checks.
SC-43Usage RestrictionsSCRequiring authorization for listed components ensures authentication occurs before critical functions are invoked.
SC-7Boundary ProtectionSCPublic components are isolated in separate subnetworks and critical internal functions are reachable only via controlled interfaces.
AC-25Reference MonitorACGuarantees critical functions are protected by mandatory invocation of the access control mechanism.
PL-11Baseline TailoringPLTailoring determines which functions require authentication and selects the appropriate baseline or compensating authentication controls.
PL-4Rules of BehaviorPLRules require authentication prior to system or function access, making missing authentication for critical functions harder to ignore or bypass.
PL-8Security and Privacy ArchitecturesPLThe control requires architectures to identify and protect critical functions, including mandatory authentication for those functions.
RA-3Risk AssessmentRARisk assessments evaluate exposure of critical functions lacking authentication and prioritize corrective controls.
RA-5Vulnerability Monitoring and ScanningRATools routinely check for missing authentication on critical functions and exposed interfaces.
RA-9Criticality AnalysisRAExplicit identification of critical functions enables targeted authentication requirements, preventing missing authentication for those functions.
CA-2Control AssessmentsCAThe assessment process confirms authentication is present and effective for critical functions, preventing exploitation from missing authentication.
CA-4Security CertificationCACertification assesses that critical functions have required authentication controls in place.
PM-5System InventoryPMKnowing every system allows confirmation that critical functions are not left without required authentication mechanisms.
PM-8Critical Infrastructure PlanPMProtection planning for critical infrastructure directly calls for authentication of access to essential functions before any operation is permitted.
AU-14Session AuditAUAuditing sessions makes it possible to detect access to critical functions without required authentication.
CM-7Least FunctionalityCMDisabling non-essential functions and services eliminates the need to secure them, reducing exposure from missing authentication on unnecessary components.
MA-4Nonlocal MaintenanceMAMandating authentication for nonlocal maintenance addresses missing authentication for this critical function.
PS-1Policy and ProceduresPSPolicy mandates authentication and authorization for critical functions, ensuring these controls are not omitted for personnel-managed resources.
SI-9Information Input RestrictionsSIEnsures critical input functions cannot be reached without prior authorization.

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2010-5326 KEV 10.010.00.17772016-05-13
CVE-2020-6287 KEV 10.010.00.94722020-07-14
CVE-2024-51567 KEV 10.010.00.86632024-10-29
CVE-2025-32433 KEV 10.010.00.98792025-04-16
CVE-2025-34028 KEV 10.010.00.97602025-04-22
CVE-2016-2004 9.99.80.94252016-04-21
CVE-2018-0127 9.99.80.77482018-02-08
CVE-2020-6207 KEV 9.99.80.98132020-03-10
CVE-2020-3952 KEV 9.99.80.90382020-04-10
CVE-2020-12720 9.99.80.88952020-05-08
CVE-2020-13927 KEV 9.99.80.99782020-11-10
CVE-2020-10148 KEV 9.99.80.91982020-12-29
CVE-2021-37415 KEV 9.99.80.99822021-09-01
CVE-2021-38540 9.99.80.80942021-09-09
CVE-2021-33543 9.99.80.81342021-09-13
CVE-2021-44077 KEV 9.99.80.93302021-11-29
CVE-2021-45232 9.99.80.86332021-12-27
CVE-2022-23227 KEV 9.99.80.48502022-01-14
CVE-2021-35587 KEV 9.99.80.96282022-01-19
CVE-2022-26143 KEV 9.99.80.87322022-03-10
CVE-2022-26501 KEV 9.99.80.04102022-03-17
CVE-2022-1388 KEV 9.99.80.99952022-05-05
CVE-2022-21587 KEV 9.99.80.98342022-10-18
CVE-2023-28461 KEV 9.99.80.68082023-03-15
CVE-2023-42793 KEV 9.99.80.99992023-09-19