结构: Simple
Abstraction: Base
状态: Draft
被利用可能性: Medium
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.
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.
cwe_Nature: ChildOf cwe_CWE_ID: 345 cwe_View_ID: 1000 cwe_Ordinal: Primary
cwe_Nature: ChildOf cwe_CWE_ID: 345 cwe_View_ID: 1003 cwe_Ordinal: Primary
cwe_Nature: ChildOf cwe_CWE_ID: 345 cwe_View_ID: 699 cwe_Ordinal: Primary
cwe_Nature: ChildOf cwe_CWE_ID: 754 cwe_View_ID: 1000
cwe_Nature: PeerOf cwe_CWE_ID: 353 cwe_View_ID: 1000
Language: {'cwe_Class': 'Language-Independent', 'cwe_Prevalence': 'Undetermined'}
范围 | 影响 | 注释 |
---|---|---|
['Integrity', 'Other'] | ['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'] | Other | Data that is parsed and used may be corrupted. |
['Non-Repudiation', 'Other'] | ['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. |
策略:
Ensure that the checksums present in messages are properly checked in accordance with the protocol specification before they are parsed and used.
The following example demonstrates the weakness.
bad C
bad Java
映射的分类名 | ImNode ID | Fit | Mapped Node Name |
---|---|---|---|
CLASP | Failure to check integrity check value |