CWE-267Privilege Defined With Unsafe Actions

Description

Common consequences· 1

• Access Control — Gain Privileges or Assume Identity
  A user can access restricted functionality and/or sensitive information that may include administrative functionality and user accounts.

Potential mitigations· 2

• [Architecture and Design, Operation]Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
• [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.

Related CAPEC attack patterns· 5

Exploits (incoming)5

(incoming)19

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.