Description
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.
Modes of Introduction:
– Architecture and Design
Likelihood of Exploit: High
Related Weaknesses
Consequences
Access Control: Gain Privileges or Assume Identity
A user can be given or gain access rights of another user. This can give the user unauthorized access to sensitive information including the access information of another user.
Potential Mitigations
Phase: Architecture and Design
Description:
Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
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-2005-1736
- Chaining of user rights.
- CVE-2002-1772
- Gain certain rights via privilege chaining in alternate channel.
- CVE-2005-1973
- Application is allowed to assign extra permissions to itself.
- CVE-2003-0640
- “operator” user can overwrite usernames and passwords to gain admin privileges.