Description
A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.
Modes of Introduction:
– Architecture and Design
Related Weaknesses
Consequences
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
Phase: Architecture and Design, Operation
Description:
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Phase: Architecture and Design, Operation
Description:
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.
CVE References
- CVE-1999-1193
- untrusted user placed in unix “wheel” group
- CVE-2005-2741
- Product allows users to grant themselves certain rights that can be used to escalate privileges.
- CVE-2005-2496
- Product uses group ID of a user instead of the group, causing it to run with different privileges. This is resultant from some other unknown issue.
- CVE-2004-0274
- Product mistakenly assigns a particular status to an entity, leading to increased privileges.