Incorrect Privilege Assignment

Opis

A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.

Skutki

• Access Control

  Gain Privileges or Assume Identity

  A user can access restricted functionality and/or sensitive information that may include administrative functionality and user accounts.

Zapobieganie

• 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.

Przykłady podatności

• CVE-1999-1193 untrusted user placed in unix "wheel" group
• CVE-2005-2741 Product allows users to grant themselves certain rights that can be used to escalate privileges.
• CVE-2005-2496 Product uses group ID of a user instead of the group, causing it to run with different privileges. This is resultant from some other unknown issue.
• CVE-2004-0274 Product mistakenly assigns a particular status to an entity, leading to increased privileges.

Słabość nadrzędna

• CWE-269 Improper Privilege Management

Może też być

• CWE-286 Incorrect User Management

Słabości podrzędne

• CWE-9 J2EE Misconfiguration: Weak Access Permissions for EJB Methods
• CWE-520 .NET Misconfiguration: Use of Impersonation
• CWE-556 ASP.NET Misconfiguration: Use of Identity Impersonation
• CWE-1022 Use of Web Link to Untrusted Target with window.opener Access
• CWE-1268 Policy Privileges are not Assigned Consistently Between Control and Data Agents

Kiedy powstaje

• Implementation — REALIZATION: This weakness is caused during implementation of an architectural security tactic.

Dotyczy

Not Language-Specific

Źródła

1. Least Privilege — Sean Barnum, Michael Gegick, 2005