The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 724 | OWASP Top Ten 2004 Category A3 - Broken Authentication and Session Management |
| MemberOf | Prohibited | C | 949 | SFP Secondary Cluster: Faulty Endpoint Authentication |
| MemberOf | Prohibited | V | 1003 | Weaknesses for Simplified Mapping of Published Vulnerabilities |
| MemberOf | Prohibited | C | 1014 | Identify Actors |
| MemberOf | Prohibited | C | 1354 | OWASP Top Ten 2021 Category A08:2021 - Software and Data Integrity Failures |
| MemberOf | Prohibited | C | 1411 | Comprehensive Categorization: Insufficient Verification of Data Authenticity |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | BS | BOSS-294 | Not Language-Specific Weaknesses |
| MemberOf | Prohibited | BS | BOSS-305 | ICS/OT (technology class) Weaknesses |
| MemberOf | Prohibited | BS | BOSS-315 | Unexpected State (impact) |
| MemberOf | Prohibited | BS | BOSS-326 | Varies by Context (impact) |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 1014 | Identify Actors |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 1354 | OWASP Top Ten 2021 Category A08:2021 - Software and Data Integrity Failures |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 949 | SFP Secondary Cluster: Faulty Endpoint Authentication |
| Scope | Likelihood | Impact | Note |
|---|---|---|---|
| IntegrityOther | N/A | Varies by ContextUnexpected State | N/A |
N/A
REALIZATION: This weakness is caused during implementation of an architectural security tactic.
In 2022, the OT:ICEFALL study examined products by 10 different Operational Technology (OT) vendors. The researchers reported 56 vulnerabilities and said that the products were "insecure by design" [REF-1283]. If exploited, these vulnerabilities often allowed adversaries to change how the products operated, ranging from denial of service to changing the code that the products executed. Since these products were often used in industries such as power, electrical, water, and others, there could even be safety implications.
Multiple vendors did not sign firmware images.
| Reference | Description |
|---|---|
| CVE-2022-30260 | Distributed Control System (DCS) does not sign firmware images and only relies on insecure checksums for integrity checks |
| CVE-2022-30267 | Distributed Control System (DCS) does not sign firmware images and only relies on insecure checksums for integrity checks |
| CVE-2022-30272 | Remote Terminal Unit (RTU) does not use signatures for firmware images and relies on insecure checksums |
| Ordinality | Description |
|---|
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
N/A
This CWE entry is a level-1 Class (i.e., a child of a Pillar). It might have lower-level children that would be more appropriate
Examine children of this entry to see if there is a better fit
"origin validation" could fall under this.
N/A
The specific ways in which the origin is not properly identified should be laid out as separate weaknesses. In some sense, this is more like a category.
N/A
| Taxonomy Name | Entry ID | Fit | Entry Name |
|---|---|---|---|
| PLOVER | N/A | N/A | Insufficient Verification of Data |
| OWASP Top Ten 2004 | A3 | CWE More Specific | Broken Authentication and Session Management |
| WASC | 12 | N/A | Content Spoofing |
| ID | Name |
|---|---|
| CAPEC-111 | JSON Hijacking (aka JavaScript Hijacking) |
| CAPEC-141 | Cache Poisoning |
| CAPEC-142 | DNS Cache Poisoning |
| CAPEC-148 | Content Spoofing |
| CAPEC-218 | Spoofing of UDDI/ebXML Messages |
| CAPEC-384 | Application API Message Manipulation via Man-in-the-Middle |
| CAPEC-385 | Transaction or Event Tampering via Application API Manipulation |
| CAPEC-386 | Application API Navigation Remapping |
| CAPEC-387 | Navigation Remapping To Propagate Malicious Content |
| CAPEC-388 | Application API Button Hijacking |
| CAPEC-665 | Exploitation of Thunderbolt Protection Flaws |
| CAPEC-701 | Browser in the Middle (BiTM) |