BaseDraft

CWE-353Missing Support for Integrity Check

Category: other

Description

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. If integrity check values or "checksums" are omitted from a protocol, there is no way of determining if data has been corrupted in transmission. The lack of checksum functionality in a protocol removes the first application-level check of data that can be used. 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.

Common consequences· 2

  • Integrity / Other — Other
    Data that is parsed and used may be corrupted.
  • Non-Repudiation / Other — Hide Activities, Other
    Without a checksum it is impossible to determine if any changes have been made to the data after it was sent.

Potential mitigations· 2

  • [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.

Related CAPEC attack patterns· 7

CAPEC-13CAPEC-14CAPEC-389CAPEC-39CAPEC-665CAPEC-74CAPEC-75

References

  1. https://cwe.mitre.org/data/definitions/353.html

Exploits (incoming)7

TypeTargetConfidenceTier
AttackPatternSubverting Environment Variable Valuescapec-13100%live
AttackPatternClient-side Injection-induced Buffer Overflowcapec-14100%live
AttackPatternManipulating Opaque Client-based Data Tokenscapec-39100%live
AttackPatternManipulating Statecapec-74100%live
AttackPatternContent Spoofing Via Application API Manipulationcapec-389100%live
AttackPatternExploitation of Thunderbolt Protection Flawscapec-665100%live
AttackPatternManipulating Writeable Configuration Filescapec-75100%live

Compliance frameworks addressing this (incoming)1

TypeTargetConfidenceTier
ComplianceControlowasp_top10-a08100%live

(incoming)2

TypeTargetConfidenceTier
VulnerabilityCVE-2026-3856cve-2026-38560%live
KEVEntryTrend Micro Apex One and Apex One as a Service Improper Validation Vulnerabilitykev-cve-2022-401390%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
Improper Validation of Integrity Check Value
CWE
Improper Enforcement of Message Integrity During Transmission in a Communication Channel
CWE
Hardware Logic with Insecure De-Synchronization between Control and Data Channels
CWE
Insufficient Verification of Data Authenticity
CWE
Missing Security-Relevant Feedback for Unexecuted Operations in Hardware Interface
CWE
Improperly Implemented Security Check for Standard
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.