Strategy: Separation of Privilege 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.
Strategy: 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.
No detection method information available for this CWE.
No examples or observed CVEs available for this CWE.
No relationship information available for this CWE.
CWE-268: CWE-268: Privilege Chaining is a Common Weakness Enumeration (CWE) entry maintained by MITRE. Description
If exploited, CWE-268 (CWE-268: Privilege Chaining) it can compromise Gain Privileges or Assume Identity, leading to outcomes such as Scope: Access Control 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..
Recommended mitigations for CWE-268 include: Strategy: Separation of Privilege 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. Strategy: 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.
CWE-268 commonly affects Languages. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
A CWE (Common Weakness Enumeration) like CWE-268 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.