The product 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 product in an invalid state.
View on MITREAlways 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.
No detection method information available for this CWE.
Special file system allows attackers to prevent ownership/permission change of certain entries by opening the entries before calling a setuid program.
View DetailsFTP server places a user in the root directory when the user's permissions prevent access to the their own home directory.
View DetailsNo relationship information available for this CWE.
CWE-280: Improper Handling of Insufficient Permissions or Privileges is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product 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 product in an invalid state.
If exploited, CWE-280 (Improper Handling of Insufficient Permissions or Privileges ) it can compromise Other, leading to outcomes such as Other and Alter Execution Logic.
Recommended mitigations for CWE-280 include: 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.
CWE-280 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
MITRE documents real CVEs mapped to CWE-280, including CVE-2003-0501 and CVE-2004-0148. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.
A CWE (Common Weakness Enumeration) like CWE-280 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.