CWE · MITRE source
CWE-924Improper Enforcement of Message Integrity During Transmission in a Communication Channel
The product establishes a communication channel with an endpoint and receives a message from that endpoint, but it does not sufficiently ensure that the message was not modified during transmission.
Attackers might be able to modify the message and spoof the endpoint by interfering with the data as it crosses the network or by redirecting the connection to a system under their control.
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 · 5 mapping(s) from 2 framework(s): STIG oracle linux 8 4 (mostly) · ATT&CK 1 (mostly)
NIST 800-53 r5 controls that address this weakness (1)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-8 | Transmission Confidentiality and Integrity | SC | The control directly mandates integrity protection for transmitted information, addressing failures to enforce message integrity in transit. |
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-2020-5869 | 7.0 | 9.1 | 0.0049 | 2020-04-24 |
CVE-2024-3596 | 7.0 | 9.0 | 0.1486 | 2024-07-09 |
CVE-2024-44730 | 7.0 | 9.1 | 0.0042 | 2024-10-11 |
CVE-2025-29628 UPD | 7.0 | 9.4 | 0.0027 | 2025-07-25 |
CVE-2018-7295 | 5.5 | 8.1 | 0.0042 | 2018-05-23 |
CVE-2021-41034 | 5.5 | 8.1 | 0.0039 | 2021-09-29 |
CVE-2021-34793 | 5.5 | 8.6 | 0.0065 | 2021-10-27 |
CVE-2022-3166 | 5.5 | 7.5 | 0.0068 | 2022-12-16 |
CVE-2023-2885 | 5.5 | 8.1 | 0.0030 | 2023-05-25 |
CVE-2023-49933 | 5.5 | 7.5 | 0.0038 | 2023-12-14 |
CVE-2023-6408 | 5.5 | 8.1 | 0.0032 | 2024-02-14 |
CVE-2020-11639 | 5.5 | 7.8 | 0.0013 | 2024-07-23 |
CVE-2024-43450 | 5.5 | 7.5 | 0.0056 | 2024-11-12 |
CVE-2024-8933 | 5.5 | 7.5 | 0.0028 | 2024-11-13 |
CVE-2024-12399 | 5.5 | 7.1 | 0.0017 | 2025-01-17 |
CVE-2025-0592 | 5.5 | 8.8 | 0.0033 | 2025-02-14 |
CVE-2019-25719 UPD | 5.5 | 8.6 | 0.0013 | 2026-06-02 |
CVE-2026-12576 | 5.5 | 7.5 | 0.0015 | 2026-07-01 |
CVE-2018-14526 | 3.5 | 6.5 | 0.0140 | 2018-08-08 |
CVE-2019-20844 | 3.5 | 6.5 | 0.0043 | 2020-06-19 |
CVE-2021-21390 | 3.5 | 6.5 | 0.0085 | 2021-03-19 |
CVE-2020-10635 | 3.5 | 4.3 | 0.0034 | 2022-02-24 |
CVE-2023-22372 | 3.5 | 5.9 | 0.0022 | 2023-05-03 |
CVE-2023-3347 | 3.5 | 5.9 | 0.0039 | 2023-07-20 |
CVE-2023-43297 | 3.5 | 5.4 | 0.0021 | 2023-10-02 |