Description
The product does not properly manage privileges while it is switching between different contexts that have different privileges or spheres of control.
Potential Impact
Access Control
Gain Privileges or Assume Identity
Mitigations & Prevention
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
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.
Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
Real-World CVE Examples
| CVE ID | Description |
|---|---|
| CVE-2002-1688 | Web browser cross domain problem when user hits "back" button. |
| CVE-2003-1026 | Web browser cross domain problem when user hits "back" button. |
| CVE-2002-1770 | Cross-domain issue - third party product passes code to web browser, which executes it in unsafe zone. |
| CVE-2005-2263 | Run callback in different security context after it has been changed from untrusted to trusted. * note that "context switch before actions are completed" is one type of problem that happens frequently |
Related Weaknesses
Taxonomy Mappings
- PLOVER: — Privilege Context Switching Error
Frequently Asked Questions
What is CWE-270?
CWE-270 (Privilege Context Switching Error) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. The product does not properly manage privileges while it is switching between different contexts that have different privileges or spheres of control.
How can CWE-270 be exploited?
Attackers can exploit CWE-270 (Privilege Context Switching Error) to gain privileges or assume identity. This weakness is typically introduced during the Architecture and Design, Implementation, Operation phase of software development.
How do I prevent CWE-270?
Key mitigations include: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
What is the severity of CWE-270?
CWE-270 is classified as a Base-level weakness (Medium abstraction). It has been observed in 4 real-world CVEs.