CWE · MITRE source
CWE-294Authentication Bypass by Capture-replay
A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes).
Capture-replay attacks are common and can be difficult to defeat without cryptography. They are a subset of network injection attacks that rely on observing previously-sent valid commands, then changing them slightly if necessary and resending the same commands to the server.
Last updated: 20 August 2026 20:22 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 · 11 mapping(s) from 2 framework(s): CAPEC 6 (partial) · ATT&CK 5 (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.
NIST 800-53 r5 controls that address this weakness (4)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-23 | Session Authenticity | SC | Protects against replay of captured session tokens or credentials by requiring authenticated, fresh session channels. |
SC-40 | Wireless Link Protection | SC | Wireless link protections commonly incorporate replay protection, reducing the exploitability of capture-replay weaknesses. |
SC-45 | System Time Synchronization | SC | Accurate synchronized time enables tight timestamp windows that directly limit capture-replay windows in authentication protocols. |
AC-9 | Previous Logon Notification | AC | Allows detection of capture-replay attacks by showing the replayed logon's timestamp as the last logon. |
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2023-23397 KEV UPD | 9.9 | 9.8 | 0.9741 | 2023-03-14 |
CVE-2017-3191 UPD | 9.6 | 9.8 | 0.6253 | 2017-12-16 |
CVE-2023-49231 UPD | 9.2 | 9.8 | 0.4290 | 2024-03-29 |
CVE-2022-22806 UPD | 8.3 | 9.8 | 0.1226 | 2022-03-09 |
CVE-2017-6034 UPD | 7.9 | 9.8 | 0.0518 | 2017-06-30 |
CVE-2018-7790 UPD | 7.7 | 9.8 | 0.0248 | 2018-08-29 |
CVE-2019-18226 UPD | 7.6 | 9.8 | 0.0137 | 2019-10-31 |
CVE-2018-17932 UPD | 7.6 | 9.8 | 0.0151 | 2020-11-02 |
CVE-2018-19025 UPD | 7.6 | 9.8 | 0.0151 | 2020-11-02 |
CVE-2022-29334 UPD | 7.5 | 9.8 | 0.0122 | 2022-05-24 |
CVE-2022-37011 UPD | 7.5 | 9.8 | 0.0112 | 2022-09-13 |
CVE-2023-30909 UPD | 7.5 | 9.8 | 0.0106 | 2023-09-14 |
CVE-2025-49752 | 7.5 | 10.0 | 0.0091 | 2025-11-20 |
CVE-2017-6823 UPD | 7.4 | 8.8 | 0.0804 | 2017-03-12 |
CVE-2017-11786 UPD | 7.4 | 8.8 | 0.0939 | 2017-10-13 |
CVE-2022-44457 UPD | 7.4 | 9.8 | 0.0072 | 2022-11-08 |
CVE-2023-1537 UPD | 7.4 | 9.8 | 0.0084 | 2023-03-21 |
CVE-2023-47435 UPD | 7.4 | 9.8 | 0.0063 | 2024-04-19 |
CVE-2024-38438 UPD | 7.4 | 9.8 | 0.0066 | 2024-07-21 |
CVE-2026-11856 | 7.4 | 9.8 | 0.0060 | 2026-07-03 |
CVE-2020-35551 UPD | 7.3 | 9.8 | 0.0042 | 2020-12-18 |
CVE-2026-28564 | 7.3 | 9.8 | 0.0044 | 2026-07-10 |
CVE-2026-68079 | 7.3 | 9.8 | 0.0041 | 2026-08-06 |
CVE-2018-17903 UPD | 7.2 | 9.1 | 0.0156 | 2018-10-24 |
CVE-2025-65552 UPD | 7.2 | 9.8 | 0.0036 | 2026-01-12 |