Katalog CWE

CWE-268 · Słabość

Privilege Chaining

Abstrakcja
Bazowa
Status
Szkic
Ryzyko wykorzystania
wysokie
Dodano
19 lipca 2006
Ostatnia zmiana
29 czerwca 2023

Podatności CVE z tą słabościąPełny wpis na cwe.mitre.org ↗

Opis

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.

Skutki

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

Zapobieganie

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

Przykłady podatności

Słabość nadrzędna

Kiedy powstaje

Dotyczy

Not Language-Specific

Uwagi

There is some conceptual overlap with Unsafe Privilege.

Źródła

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

Wpis z katalogu CWE 4.20.