CWE-268: Privilege Chaining
Weakness ID: 268 (Weakness Base) Status: Draft
Description
Description Summary
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.
Time of Introduction
Architecture and Design
Implementation
Operation
Likelihood of Exploit
Observed Examples
Reference Description 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.
Potential Mitigations
ID Phase Description Consider following the principle of separation of privilege. Require
multiple conditions to be met before permitting access to a system
resource.
1 Very carefully manage the setting, management and handling of
privileges. Explicitly manage trust zones in the software.
Follow the principle of least privilege when assigning access rights
to entities in a software system.
Other Notes
It is difficult to find good examples for this weakness.
Weakness Ordinalities
Ordinality Description Primary
(where the
weakness exists independent of other weaknesses)
Relationships
Relationship Notes
There is some conceptual overlap with Unsafe Privilege.
Causal Nature
Taxonomy Mappings
Mapped Taxonomy Name Node ID Fit Mapped Node Name PLOVER Privilege Chaining
Content History
Submissions Submission Date Submitter Organization Source PLOVER Externally Mined Modifications Modification Date Modifier Organization Source 2008-07-01 Eric Dalci Cigital External updated Time of Introduction 2008-09-08 CWE Content Team MITRE Internal updated Relationships, Other Notes, Relationship Notes,
Taxonomy Mappings, Weakness Ordinalities 2009-03-10 CWE Content Team MITRE Internal updated Relationships
Description
