CWE-353: Missing Support for Integrity Check
48 CVEs have CWE-353 as their primary weakness. 0 of them are in the CISA KEV catalog. The highest EPSS score among them is 2.514%.
The product uses a transmission protocol that does not include a mechanism for verifying the integrity of the data during transmission, such as a checksum.
The end-to-end philosophy of checks states that integrity checks should be performed at the lowest level that they can be completely implemented. Excluding further sanity checks and input validation performed by applications, the protocol's checksum is the most important level of checksum, since it can be performed more completely than at any previous level and takes into account entire messages, as opposed to single packets.
Child of CWE-345: Insufficient Verification of Data Authenticity
Mitigations
- Architecture and Design: Add an appropriately sized checksum to the protocol, ensuring that data received may be simply validated before it is parsed and used.
- Implementation: Ensure that the checksums present in the protocol design are properly implemented and added to each message before it is sent.
Observed examples
- CVE-2025-32890: Mesh device uses a cryptographic algorithm without integrity checking, allowing modification of messages
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-353'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-353'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).