The product does not handle or incorrectly handles when it has insufficient privileges to perform an operation, leading to resultant weaknesses.
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| CanAlsoBe | Allowed | B | 280 | Improper Handling of Insufficient Permissions or Privileges |
| ChildOf | Discouraged | C | 755 | Improper Handling of Exceptional Conditions |
| ChildOf | Discouraged | C | 269 | Improper Privilege Management |
| PeerOf | Allowed-with-Review | C | 271 | Privilege Dropping / Lowering Errors |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 265 | Privilege Issues |
| MemberOf | Prohibited | C | 901 | SFP Primary Cluster: Privilege |
| MemberOf | Prohibited | C | 1011 | Authorize Actors |
| MemberOf | Prohibited | C | 1396 | Comprehensive Categorization: Access Control |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | BS | BOSS-294 | Not Language-Specific Weaknesses |
| MemberOf | Prohibited | BS | BOSS-312 | Other (impact) |
| MemberOf | Prohibited | BS | BOSS-330 | Alter Execution Logic (impact) |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 1011 | Authorize Actors |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 265 | Privilege Issues |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 901 | SFP Primary Cluster: Privilege |
| Scope | Likelihood | Impact | Note |
|---|---|---|---|
| Other | N/A | OtherAlter Execution Logic | N/A |
REALIZATION: This weakness is caused during implementation of an architectural security tactic.
N/A
| Reference | Description |
|---|---|
| CVE-2001-1564 | System limits are not properly enforced after privileges are dropped. |
| CVE-2005-3286 | Firewall crashes when it can't read a critical memory block that was protected by a malicious process. |
| CVE-2005-1641 | Does not give admin sufficient privileges to overcome otherwise legitimate user actions. |
| Ordinality | Description |
|---|---|
| Primary | N/A |
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
N/A
This CWE entry could be deprecated in a future version of CWE.
See maintenance notes.
CWE-280 and CWE-274 are too similar. It is likely that CWE-274 will be deprecated in the future.
N/A
Overlaps dropped privileges, insufficient permissions.
N/A
This has a layering relationship with Unchecked Error Condition and Unchecked Return Value.
N/A
Within the context of vulnerability theory, privileges and permissions are two sides of the same coin. Privileges are associated with actors, and permissions are associated with resources. To perform access control, at some point the product makes a decision about whether the actor (and the privileges that have been assigned to that actor) is allowed to access the resource (based on the permissions that have been specified for that resource).
N/A
| Taxonomy Name | Entry ID | Fit | Entry Name |
|---|---|---|---|
| PLOVER | N/A | N/A | Insufficient privileges |
| ID | Name |
|---|