The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
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.
Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
CVE-2001-1555Terminal privileges are not reset when a user logs out.
CVE-2001-1514Does not properly pass security context to child processes in certain cases, allows privilege escalation.
CVE-2001-0128Does not properly compute roles.
CVE-1999-1193untrusted user placed in unix "wheel" group
CVE-2005-2741Product allows users to grant themselves certain rights that can be used to escalate privileges.