CWE · MITRE source
CWE-420Unprotected Alternate Channel
The product protects a primary channel, but it does not use the same level of protection for an alternate channel.
Last updated: 04 July 2026 00:28 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 1 framework(s): ATT&CK 3 (mostly)
NIST 800-53 r5 controls that address this weakness (3)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
AC-17 | Remote Access | AC | Usage restrictions and authorization for remote access protect against unprotected alternate channels. |
RA-6 | Technical Surveillance Countermeasures Survey | RA | TSCM surveys detect and neutralize unprotected alternate channels introduced by surveillance equipment or modifications. |
SC-41 | Port and I/O Device Access | SC | Removes or disables unprotected alternate I/O channels that could otherwise be used to bypass primary controls. |
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). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2023-20198 KEV | 10.0 | 10.0 | 0.9957 | 2023-10-16 |
CVE-2025-54309 KEV UPD | 10.0 | 9.0 | 0.9203 | 2025-07-18 |
CVE-2024-10081 | 7.0 | 10.0 | 0.4006 | 2024-11-06 |
CVE-2025-52921 UPD | 7.0 | 9.9 | 0.0047 | 2025-06-23 |
CVE-2025-13315 | 7.0 | 9.8 | 0.3194 | 2025-11-19 |
CVE-2023-28840 | 5.5 | 7.5 | 0.0273 | 2023-04-04 |
CVE-2023-31241 | 5.5 | 8.6 | 0.0076 | 2023-05-22 |
CVE-2023-4570 | 5.5 | 8.8 | 0.0028 | 2023-10-05 |
CVE-2024-8038 | 5.5 | 7.9 | 0.0021 | 2024-10-02 |
CVE-2023-7266 | 5.5 | 7.5 | 0.0027 | 2024-12-28 |
CVE-2025-1095 | 5.5 | 8.8 | 0.0013 | 2025-04-08 |
CVE-2025-54351 UPD | 5.5 | 8.9 | 0.0038 | 2025-08-03 |
CVE-2025-59033 | 5.5 | 7.4 | 0.0022 | 2025-09-08 |
CVE-2025-8557 | 5.5 | 8.8 | 0.0024 | 2025-09-11 |
CVE-2025-53967 | 5.5 | 8.0 | 0.0742 | 2025-10-08 |
CVE-2025-62001 | 5.5 | 8.8 | 0.0033 | 2025-12-18 |
CVE-2025-67303 | 5.5 | 7.5 | 0.0136 | 2026-01-05 |
CVE-2025-41727 | 5.5 | 7.8 | 0.0016 | 2026-01-27 |
CVE-2026-40217 UPD | 5.5 | 8.8 | 0.0650 | 2026-04-10 |
CVE-2020-8558 | 3.5 | 5.4 | 0.0360 | 2020-07-27 |
CVE-2022-25786 | 3.5 | 4.9 | 0.0069 | 2022-05-04 |
CVE-2023-28842 | 3.5 | 6.8 | 0.0144 | 2023-04-04 |
CVE-2023-0317 | 3.5 | 4.9 | 0.0052 | 2023-04-19 |
CVE-2024-4444 | 3.5 | 5.3 | 0.0071 | 2024-05-14 |
CVE-2024-6099 | 3.5 | 5.3 | 0.0042 | 2024-07-02 |