CWE-268: Privilege Chaining
CWE版本: 4.18
更新日期: 2025-09-09
弱点描述
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.
常见后果
影响范围: 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.
潜在缓解措施
阶段: Architecture and Design
策略: Separation of Privilege
描述: Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
阶段: 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
策略: Environment Hardening
描述: 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-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.
引入模式
| 阶段 | 说明 |
|---|---|
| Architecture and Design | - |
| Implementation | REALIZATION: This weakness is caused during implementation of an architectural security tactic. |
| Operation | - |
适用平台
编程语言
分类映射
| 分类名称 | 条目ID | 条目名称 | 映射适配度 |
|---|---|---|---|
| PLOVER | - | Privilege Chaining | - |