CWE - CWE-354: Improper Validation of Integrity Check Value (2.11)

Weakness ID: 354

Abstraction: Base

Status: Draft

Presentation Filter:

Description

Description Summary

The software 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.

Time of Introduction

Architecture and Design
Implementation

Applicable Platforms

Languages

All

Common Consequences

Scope	Effect
Integrity Other	Technical Impact: Modify application data; 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.
Integrity Other	Technical Impact: Other Data that is parsed and used may be corrupted.
Non-Repudiation Other	Technical Impact: Hide activities; Other Without a checksum check, it is impossible to determine if any changes have been made to the data after it was sent.

Likelihood of Exploit

Medium

Demonstrative Examples

Example 1

(Bad Code)

Example Languages: C and C++

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);

}

(Bad Code)

Example Language: Java

while(true) {

DatagramPacket packet = new DatagramPacket(data,data.length,IPAddress, port);

socket.send(sendPacket);

}

Potential Mitigations

Phase: Implementation

Ensure that the checksums present in messages are properly checked in accordance with the protocol specification before they are parsed and used.

Relationships

Nature	Type	ID	Name	View(s) this relationship pertains to
ChildOf	Weakness Class	345	Insufficient Verification of Data Authenticity	Development Concepts (primary)699 Research Concepts (primary)1000
ChildOf	Weakness Class	754	Improper Check for Unusual or Exceptional Conditions	Research Concepts1000
ChildOf	Category	993	SFP Secondary Cluster: Incorrect Input Handling	Software Fault Pattern (SFP) Clusters (primary)888
PeerOf	Weakness Base	353	Missing Support for Integrity Check	Research Concepts1000
MemberOf	View	884	CWE Cross-section	CWE Cross-section (primary)884

Taxonomy Mappings

Mapped Taxonomy Name	Node ID	Fit	Mapped Node Name
CLASP			Failure to check integrity check value

Related Attack Patterns

CAPEC-ID	Attack Pattern Name	(CAPEC Version: 2.10)
CAPEC-463	Padding Oracle Crypto Attack
CAPEC-75	Manipulating Writeable Configuration Files

Content History

Submissions
Submission Date	Submitter	Organization	Source
	CLASP		Externally Mined

Modifications
Modification Date	Modifier	Organization	Source
2008-07-01	Eric Dalci	Cigital	External
2008-07-01	updated Time_of_Introduction
2008-09-08	CWE Content Team	MITRE	Internal
2008-09-08	updated Common_Consequences, Relationships, Other_Notes, Taxonomy_Mappings
2009-03-10	CWE Content Team	MITRE	Internal
2009-03-10	updated Description, Name, Relationships
2009-10-29	CWE Content Team	MITRE	Internal
2009-10-29	updated Description, Other_Notes
2010-12-13	CWE Content Team	MITRE	Internal
2010-12-13	updated Description
2011-06-01	CWE Content Team	MITRE	Internal
2011-06-01	updated Common_Consequences
2012-05-11	CWE Content Team	MITRE	Internal
2012-05-11	updated Related_Attack_Patterns, Relationships
2014-07-30	CWE Content Team	MITRE	Internal
2014-07-30	updated Relationships
Previous Entry Names
Change Date	Previous Entry Name
2009-03-10	Failure to Check Integrity Check Value


	Use of the Common Weakness Enumeration and the associated references from this website are subject to the Terms of Use. For more information, please email cwe@mitre.org. CWE is sponsored by US-CERT in the office of Cybersecurity and Communications at the U.S. Department of Homeland Security. Copyright © 2006-2017, The MITRE Corporation. CWE, CWSS, CWRAF, and the CWE logo are trademarks of The MITRE Corporation.	Privacy policy Terms of use Contact us

Common Weakness Enumeration

CWE-354: Improper Validation of Integrity Check Value