CWE-354: Improper Validation of Integrity Check Value

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.

Code Examples & CVEs

Demonstrative Examples

The following example demonstrates the weakness.

BadC

sd = socket(AF_INET, SOCK_DGRAM, 0); serv.sin_family = AF_INET;serv.sin_addr.s_addr = htonl(INADDR_ANY);servr.sin_port = htons(1008);bind(sd, (struct sockaddr *) & serv, sizeof(serv));while (1) {                                                     memset(msg, 0x0, MAX_MSG);clilen = sizeof(cli);if (inet_ntoa(cli.sin_addr)==...) n = recvfrom(sd, msg, MAX_MSG, 0, (struct sockaddr *) & cli, &clilen);                      }

The following example demonstrates the weakness.

BadJava

while(true) {DatagramPacket packet = new DatagramPacket(data,data.length,IPAddress, port);socket.send(sendPacket);}

Observed CVE Examples (1)

CVE-2024-47573

network analysis tool does not properly validate an integrity check value, allowing installation of malicious firmware

View Details

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-354 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-354, Improper Validation of Integrity Check Value, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Improper Validation of Integrity Check Value during Implementation

MITRE associates mitigation with Implementation; recorded impacts include Modify Application Data, Other, and Hide Activities; the entry maps to CAPEC-145, CAPEC-463, and CAPEC-75. Use these source-defined anchors to turn CWE-354 into implementation, review, and verification checks for the affected component.

CWE-354: Improper Validation of Integrity Check Value — MITRE CWE

Triage CWE-354 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-354, Improper Validation of Integrity Check Value, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-354

Apply MITRE's full root-cause mapping guidance when using CWE-354, Improper Validation of Integrity Check Value. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-354 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-354, Improper Validation of Integrity Check Value. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-354: Improper Validation of Integrity Check Value?+

CWE-354: Improper Validation of Integrity Check Value is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Improper Validation of Integrity Check Value?+

If exploited, CWE-354 (Improper Validation of Integrity Check Value) it can compromise Integrity, Other and Non-Repudiation, leading to outcomes such as Modify Application Data, Other and Hide Activities.

How do you prevent or mitigate Improper Validation of Integrity Check Value?+

Recommended mitigations for CWE-354 include: Ensure that the checksums present in messages are properly checked in accordance with the protocol specification before they are parsed and used.

Which programming languages are affected by Improper Validation of Integrity Check Value?+

CWE-354 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Improper Validation of Integrity Check Value?+

MITRE documents real CVEs mapped to CWE-354, including CVE-2024-47573. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-354 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

CWE-354: Improper Validation of Integrity Check Value

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Scope

Impact

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods

Code Examples & CVEs

Demonstrative Examples

Observed CVE Examples (1)

CWE Relationships

Parent Weaknesses

Source-backed guidance

Verify controls for CWE-354 with SSDF evidence

Address Improper Validation of Integrity Check Value during Implementation

Triage CWE-354 against known exploitation evidence

Apply precise root-cause mapping to CWE-354

Validate CWE-354 with root-cause mapping checks

Frequently Asked Questions

Learn More