Insecure Inherited Permissions
Draft Variant
Structure: Simple
Description
A product defines a set of insecure permissions that are inherited by objects that are created by the program.
Common Consequences 1
Scope: ConfidentialityIntegrity
Impact: Read Application DataModify Application Data
Potential Mitigations 2
Phase: Architecture and DesignOperation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Phase: Architecture and Design
Strategy: 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.
Observed Examples 2
CVE-2005-1841User's umask is used when creating temp files.
CVE-2002-1786Insecure umask for core dumps [is the umask preserved or assigned?].
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Modes of Introduction
Architecture and Design
Implementation
Operation
Related Weaknesses
Taxonomy Mapping
- PLOVER