CWE-268
Privilege Chaining
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.
Parent Weaknesses (ChildOf)
Common Consequences
Scope
Impact
Gain Privileges or Assume Identity
Potential Mitigations
Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
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.
CVE-2005-1736Chaining of user rights.
CVE-2002-1772Gain certain rights via privilege chaining in alternate channel.
CVE-2005-1973Application is allowed to assign extra permissions to itself.
CVE-2003-0640"operator" user can overwrite usernames and passwords to gain admin privileges.
Applicable Platforms
Security Training
Train your team to recognize and prevent security threats with our comprehensive security awareness program.
Start TrainingVulnerability Scanning
Discover vulnerabilities in your applications and infrastructure before attackers do.
Scan Now