COMMON WEAKNESS ENUMERATIONDraft

CWE-354

Improper 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.

Abstraction

Base

Structure

Simple

Likelihood of Exploit

Medium

Understand the problem

What is the problem?

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.

Extended description

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.

Root cause

How and when does the problem arise?

Lifecycle phase

Architecture and Design

Lifecycle phase

Implementation

REALIZATION: This weakness is caused during implementation of an architectural security tactic.

Risk

What does successful exploitation lead to?

Modify Application DataOther

Affected security scopes: Integrity, Other

Integrity checks usually use a secret key that helps authenticate the data origin. Skipping integrity checking generally opens up the possibility that new data from an invalid source can be injected.
Other

Affected security scopes: Integrity, Other

Data that is parsed and used may be corrupted.
Hide ActivitiesOther

Affected security scopes: Non-Repudiation, Other

Without a checksum check, it is impossible to determine if any changes have been made to the data after it was sent.

Defence

How is it prevented and fixed?

Implementation

Implementation-phase defence

Detail
Ensure that the checksums present in messages are properly checked in accordance with the protocol specification before they are parsed and used.
CWE-354: Common Weakness Enumeration Entry CWE-354 · DayBreach Sözlük · DayBreach