CWE · MITRE source
CWE-304Missing Critical Step in Authentication
The product implements an authentication technique, but it skips a step that weakens the technique.
Authentication techniques should follow the algorithms that define them exactly, otherwise authentication can be bypassed or more easily subjected to brute force attacks.
Last updated: 15 October 2026 14:21 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: mostly · 3 mapping(s) from 2 framework(s): STIG rhel 7 2 (mostly) · STIG ubuntu 22 04 1 (mostly)
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.
—
- 6 hardening rules · 2 OS baselines
V7.2.4
NIST 800-53 r5 controls PROPOSED for this weakness (1)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.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
IA-8 | Identification and Authentication (Non-organizational Users) | IA | graded full Ensures the authentication process is followed for non-organizational users, avoiding missing critical steps. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2023-54391 | 7.8 | 9.8 | 0.0306 | 2026-09-01 |
CVE-2022-2302 UPD | 7.7 | 9.8 | 0.0214 | 2022-07-11 |
CVE-2024-2172 UPD | 7.6 | 9.8 | 0.0171 | 2024-03-13 |
CVE-2024-8954 UPD | 7.5 | 9.8 | 0.0089 | 2025-03-20 |
CVE-2026-30831 UPD | 7.4 | 9.8 | 0.0063 | 2026-03-06 |
CVE-2026-61466 | 7.0 | 9.1 | 0.0071 | 2026-08-06 |
CVE-2026-59564 UPD | 6.9 | 9.1 | 0.0053 | 2026-08-24 |
CVE-2026-44547 UPD | 6.8 | 9.6 | 0.0036 | 2026-05-12 |
CVE-2026-94052 | 6.8 | 9.1 | 0.0038 | 2026-09-30 |
CVE-2022-40622 UPD | 6.7 | 8.8 | 0.0074 | 2022-09-13 |
CVE-2024-12048 UPD | 6.7 | 8.8 | 0.0074 | 2025-03-20 |
CVE-2022-1065 UPD | 6.6 | 8.1 | 0.0289 | 2022-04-19 |
CVE-2026-67351 | 6.6 | 8.8 | 0.0056 | 2026-07-30 |
CVE-2026-49467 UPD | 6.6 | 8.8 | 0.0062 | 2026-08-12 |
CVE-2019-16766 UPD | 6.5 | 8.7 | 0.0146 | 2019-11-29 |
CVE-2024-45764 | 6.4 | 9.0 | 0.0052 | 2024-11-08 |
CVE-2024-9216 UPD | 6.2 | 8.1 | 0.0063 | 2025-03-20 |
CVE-2025-24322 UPD | 6.2 | 8.1 | 0.0057 | 2025-08-20 |
CVE-2026-55957 | 6.2 | 7.3 | 0.0285 | 2026-06-29 |
CVE-2022-2821 UPD | 6.1 | 7.5 | 0.0138 | 2022-08-15 |
CVE-2026-42452 UPD | 6.1 | 8.1 | 0.0040 | 2026-05-08 |
CVE-2026-76207 UPD | 6.1 | 8.1 | 0.0046 | 2026-08-19 |
CVE-2026-89068 | 6.1 | 8.1 | 0.0046 | 2026-10-14 |
CVE-2026-93994 | 6.0 | 8.1 | 0.0032 | 2026-09-30 |
CVE-2024-11302 UPD | 5.9 | 8.0 | 0.0023 | 2025-03-20 |