Weaknesses in this category are related to the design and architecture of a system's data integrity components. Frequently these deal with ensuring integrity of data, such as messages, resource files, deployment files, and configuration files. The weaknesses in this category could lead to a degradation of data integrity quality if they are not addressed when designing or implementing a secure architecture.
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | V | 1008 | Architectural Concepts |
| HasMember | Allowed | B | 353 | Missing Support for Integrity Check |
| HasMember | Allowed | B | 354 | Improper Validation of Integrity Check Value |
| HasMember | Allowed | B | 390 | Detection of Error Condition Without Action |
| HasMember | Prohibited | B | 391 | Unchecked Error Condition |
| HasMember | Allowed | B | 494 | Download of Code Without Integrity Check |
| HasMember | Allowed | B | 565 | Reliance on Cookies without Validation and Integrity Checking |
| HasMember | Allowed | B | 649 | Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking |
| HasMember | Discouraged | P | 707 | Improper Neutralization |
| HasMember | Discouraged | C | 755 | Improper Handling of Exceptional Conditions |
| HasMember | Allowed | B | 924 | Improper Enforcement of Message Integrity During Transmission in a Communication Channel |
This entry is a Category. Using categories for mapping has been discouraged since 2019. Categories are informal organizational groupings of weaknesses that can help CWE users with data aggregation, navigation, and browsing. However, they are not weaknesses in themselves.
See member weaknesses of this category.
| Taxonomy Name | Entry ID | Fit | Entry Name |
|---|