Incorrect Execution-Assigned Permissions

Draft Variant
Structure: Simple
Description

This vulnerability occurs when a running application incorrectly changes an object's access permissions, overriding the security settings that a user or administrator intentionally configured.

Extended Description

This flaw typically happens during an application's runtime operations, such as when it creates temporary files, spawns new processes, or modifies system resources. Instead of respecting the principle of least privilege, the software assigns broader permissions—like making a file world-writable or granting excessive privileges to a process—than what was originally intended. This creates a window of opportunity where unauthorized users or processes can read, modify, or execute sensitive resources. To prevent this, developers must ensure that permission assignments are explicit, validated, and adhere strictly to the user-specified security policy throughout the entire lifecycle of an object. Code should avoid implicit or default permission settings during execution, and security-critical functions must consistently check and apply the correct, minimal permissions required for the task.

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 3
CVE-2002-0265Log files opened read/write.
CVE-2003-0876Log files opened read/write.
CVE-2002-1694Log files opened read/write.
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Modes of Introduction
Implementation
Architecture and Design
Operation
Taxonomy Mapping
  • PLOVER
  • CERT C Secure Coding
  • The CERT Oracle Secure Coding Standard for Java (2011)