CWE-270 — Privilege Context Switching Error
CWE-270: Privilege Context Switching Error
MITRE CWE weakness
| Kind | Weakness |
| Abstraction | Base |
| Status | Draft |
| Likelihood of exploit | — |
Description
The product does not properly manage privileges while it is switching between different contexts that have different privileges or spheres of control.
Common consequences
- Access Control: Gain Privileges or Assume Identity
Mitigations
Architecture and Design — Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design — Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
Architecture and Design — Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
References
- CWE page: https://cwe.mitre.org/data/definitions/270.html
- CWE list: https://cwe.mitre.org/data/index.html