ICS Communications: Zone Boundary Failures
A category in the Common Weakness Enumeration published by The MITRE Corporation.
Categories in the Common Weakness Enumeration (CWE) group entries based on some common characteristic or attribute.
Weaknesses in this category are related to the "Zone Boundary Failures" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Within an ICS system, for traffic that crosses through network zone boundaries, vulnerabilities arise when those boundaries were designed for safety or other purposes but are being repurposed for security." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
A product requires authentication, but the product has an alternate path or channel that does not require authentication.
The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a ...
The product downloads source code or an executable from a remote location and executes the code without sufficiently verifying the origin and integrity of the code.
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the pro...
The System-On-a-Chip (SoC) does not properly isolate shared resources between trusted and untrusted agents.
The product is designed with access restricted to certain information, but it does not sufficiently protect against an unauthorized actor with physical access to these...
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the ...
The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.
The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere, in a manner that provides ...
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
Hardware structures shared across execution contexts (e.g., caches and branch predictors) can violate the expected architecture isolation between contexts.
Two distinct privileges, roles, capabilities, or rights can be combined in a way that allows an entity to perform unsafe actions that would not be allowed without that...
Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal au...
The product mixes trusted and untrusted data in the same data structure or structured message.
The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment.
The product uses default passwords for potentially critical functionality.
CWE entries in this view (graph) are associated with the Categories of Security Vulnerabilities in ICS, as published by the Securing Energy Infrastructure Executive Ta...
- Categories of Security Vulnerabilities in ICS
Securing Energy Infrastructure Executive Task Force (SEI ETF)