Insecure Inherited Permissions

Opis

A product defines a set of insecure permissions that are inherited by objects that are created by the program.

Skutki

• Confidentiality, Integrity

  Read Application Data; Modify Application Data

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 · Separation of Privilege

  Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.

  Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

Przykłady podatności

• CVE-2005-1841 User's umask is used when creating temp files.
• CVE-2002-1786 Insecure umask for core dumps [is the umask preserved or assigned?].

Słabość nadrzędna

• CWE-732 Incorrect Permission Assignment for Critical Resource

Kiedy powstaje

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

Dotyczy

Not Language-Specific