Description
The application does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. This may cause it to follow unexpected code paths that may leave the application in an invalid state.
Modes of Introduction:
– Architecture and Design
Related Weaknesses
Consequences
Other: Other, Alter Execution Logic
Potential Mitigations
Phase: Architecture and Design
Description:
Phase: Implementation
Description:
Always check to see if you have successfully accessed a resource or system functionality, and use proper error handling if it is unsuccessful. Do this even when you are operating in a highly privileged mode, because errors or environmental conditions might still cause a failure. For example, environments with highly granular permissions/privilege models, such as Windows or Linux capabilities, can cause unexpected failures.
CVE References
- CVE-2003-0501
- Special file system allows attackers to prevent ownership/permission change of certain entries by opening the entries before calling a setuid program.
- CVE-2004-0148
- FTP server places a user in the root directory when the user’s permissions prevent access to the their own home directory.