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.
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.
Impact: Read Application DataModify Application Data
Strategy: Separation of Privilege