|
|
|
|
CWE-354 Individual Dictionary Definition (Draft 9)
Weakness ID
| Status: Draft 354 (Weakness Base) | | Description | Summary If integrity check values or "checksums" are not validated before messages are parsed and
used, there is no way of determining if data has been corrupted in transmission. | | Likelihood of Exploit | Medium | | Common Consequences | Authentication: 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: Data that is parsed and used may be corrupted. Non-repudiation: Without a checksum check, it is impossible to determine if
any changes have been made to the data after it was sent. | | Potential Mitigations | Implementation: Ensure that the checksums present in messages are properly checked in
accordance with the protocol specification before they are parsed and used. | Demonstrative
Examples | C/C++ Example: 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);
} Java Example: while(true) {
DatagramPacket packet = new DatagramPacket(data,data.length,IPAddress, port);
socket.send(sendPacket);
} | | Context Notes | The failure to validate checksums before use results in an unnecessary risk that can
easily be mitigated with very few lines of code. Since the protocol specification describes the
algorithm used for calculating the checksum, it is a simple matter of implementing the calculation
and verifying that the calculated checksum and the received checksum match. If this small amount
of effort is skipped, the consequences may be far greater. | | Relationships | | | Source Taxonomies | CLASP - Failure to check integrity check value | | Applicable Platforms | All | | Related Attack Patterns | | CAPEC-ID | Attack Pattern Name |
|---|
| 75 | Manipulating Writeable Configuration Files |
|
|
- Weakness
- Base
- Variant
- Class
- Chain
- Composite
- Category
- View
- Deprecated
