CWE

Insecure Inherited Permissions

ID: 277		Date: (C)2012-05-14   (M)2022-10-10
Type: weakness		Status: DRAFT
Abstraction Type: Variant

Description

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

Applicable Platforms
Language Class: All

Time Of Introduction

• Architecture and Design
• Implementation
• Operation

Common Consequences

Scope	Technical Impact	Notes
Confidentiality Integrity	Read application data Modify application data

Detection Methods
None

Potential Mitigations

Phase	Strategy	Description	Effectiveness	Notes
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 that the compartmentalization serves to allow for and further reinforce privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide when it is appropriate to use and to drop system privileges.

Relationships

Related CWE	Type	View	Chain
CWE-277 ChildOf CWE-899	Category	CWE-888

Demonstrative Examples
None

Observed Examples

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

For more examples, refer to CVE relations in the bottom box.

White Box Definitions
None

Black Box Definitions
None

Taxynomy Mappings

Taxynomy	Id	Name	Fit
PLOVER		Insecure inherited permissions

References:
None