Skip to content
OpenAdvisories

Weakness (CWE)

CWE-268: Privilege Chaining

Base Draft

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 combination.

How to prevent it (3 mitigations)

  1. Architecture and Design

    Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.

  2. Architecture and Design, Operation

    Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.

  3. Architecture and Design, Operation

    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.

Source: MITRE CWE-268

All Critical High Medium Low Exploited only Public exploit

3 results · Clear filters · Feed