CWE · MITRE source
CWE-354Improper Validation of Integrity Check Value
The product does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission.
Improper validation of checksums before use results in an unnecessary risk that can easily be mitigated. The protocol specification describes the algorithm used for calculating the checksum. It is then a simple matter of implementing the calculation and verifying that the calculated checksum and the received checksum match. Improper verification of the calculated checksum and the received checksum can lead to far greater consequences.
Last updated: 09 May 2026 03:25 UTC
NIST 800-53 r5 controls that address this weakness (5)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-21 | Secure Name/Address Resolution Service (Recursive or Caching Resolver) | SC | Requires validation of integrity check values on every resolution response, directly mitigating tampered or corrupted DNS data. |
SC-33 | Transmission Preparation Integrity | SC | Control mandates proper validation of integrity values (checksums) on prepared data, making flawed validation of those checks ineffective for attackers. |
SA-18 | Tamper Resistance and Detection | SA | Proper validation of integrity check values is required for reliable tamper detection, directly reducing undetected modification risks. |
SI-7 | Software, Firmware, and Information Integrity | SI | Requires use of proper integrity verification tools, reducing the chance an incorrect check value is accepted. |
SR-9 | Tamper Resistance and Detection | SR | Requires proper validation of integrity mechanisms, directly mitigating flawed check-value handling. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2023-48795 | 4.4 | 5.9 | 0.5356 | 2023-12-18 |
CVE-2024-3596 | 2.9 | 9.0 | 0.1902 | 2024-07-09 |
CVE-2017-15994 | 2.0 | 9.8 | 0.0013 | 2017-10-29 |
CVE-2019-1166 | 2.0 | 5.9 | 0.1300 | 2019-10-10 |
CVE-2023-33668 | 2.0 | 9.8 | 0.0094 | 2023-07-12 |
CVE-2024-25678 | 2.0 | 9.8 | 0.0008 | 2024-02-09 |
CVE-2025-11543 | 2.0 | 9.8 | 0.0004 | 2025-12-22 |
CVE-2022-29898 | 1.9 | 9.1 | 0.0054 | 2022-05-11 |
CVE-2017-4961 | 1.8 | 8.8 | 0.0020 | 2017-06-13 |
CVE-2020-7810 | 1.8 | 8.8 | 0.0020 | 2020-08-07 |
CVE-2020-25758 | 1.8 | 8.8 | 0.0027 | 2020-12-15 |
CVE-2020-14120 | 1.8 | 8.8 | 0.0014 | 2022-04-21 |
CVE-2025-54887 | 1.8 | 9.1 | 0.0001 | 2025-08-08 |
CVE-2026-33026 | 1.8 | 9.1 | 0.0001 | 2026-03-30 |
CVE-2017-3760 | 1.7 | 8.1 | 0.0083 | 2017-10-17 |
CVE-2019-13496 | 1.7 | 8.1 | 0.0063 | 2019-11-04 |
CVE-2018-21070 | 1.7 | 8.4 | 0.0001 | 2020-04-08 |
CVE-2022-25946 | 1.7 | 8.7 | 0.0013 | 2022-05-05 |
CVE-2023-28386 | 1.7 | 8.6 | 0.0011 | 2023-05-22 |
CVE-2024-3727 | 1.7 | 8.3 | 0.0049 | 2024-05-14 |
CVE-2024-52550 | 1.7 | 8.0 | 0.0140 | 2024-11-13 |
CVE-2018-5441 | 1.6 | 7.8 | 0.0004 | 2018-01-30 |
CVE-2017-3224 | 1.6 | 8.2 | 0.0003 | 2018-07-24 |
CVE-2018-6336 | 1.6 | 7.8 | 0.0009 | 2018-12-31 |
CVE-2019-12097 | 1.6 | 7.8 | 0.0001 | 2019-06-03 |