Skip to content
OpenAdvisories

Weakness (CWE)

CWE-277: Insecure Inherited Permissions

Variant Draft

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

How to prevent it (2 mitigations)
  1. Architecture and Design, Operation

    Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.

  2. Architecture and Design

    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.

Source: MITRE CWE-277

45 results · Clear filters · Feed

  • Medium 6.7

    Insecure inherited permissions for the Intel(R) NUC Pro Software Suite before version 2.0.0.3 may allow an authenticate…

  • Medium 6.7

    Insecure inherited permissions in the HotKey Services for some Intel(R) NUC P14E Laptop Element software for Windows 10…

  • Medium 6.7

    Insecure inherited permissions in the Intel(R) VTune(TM) Profiler software before version 2023.0 may allow an authentic…

  • Medium 6.7

    Insecure inherited permissions in some Intel(R) Wireless Adapter Driver installation software for Intel(R) NUC Kits & M…

  • Medium 5.1

    An exploitable shared memory permissions vulnerability exists in the functionality of X11 Mesa 3D Graphics Library 19.1…