Weakness (CWE)
CWE-277: Insecure Inherited Permissions
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)
-
Architecture and Design, Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
-
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
3 results · Clear filters · Feed
-
Critical 9.8
Insecure permissions in external-secrets v0.9.16 allows attackers to access sensitive data and escalate privileges by o…
-
Critical 9.8CVE-2024-36539 Public exploit
Insecure permissions in contour v1.28.3 allows attackers to access sensitive data and escalate privileges by obtaining …
-
Critical 9.8
Evaluation of closures can lead to execution of methods & functions in current program scope
neoan3-apps/template is a neoan3 minimal template engine. Versions prior to 1.1.1 have allowed for passing in closures directly into the template engine. As a result values that are callable are executed by the template engine. The issue arises if a value has…