CWE-280 不充分权限或特权的处理不恰当

Improper Handling of Insufficient Permissions or Privileges

结构: Simple

Abstraction: Base

状态: Draft

被利用可能性: unkown

基本描述

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.

适用平台

Language: {'cwe_Class': 'Language-Independent', 'cwe_Prevalence': 'Undetermined'}

常见的影响

范围	影响	注释
Other	['Other', 'Alter Execution Logic']

可能的缓解方案

MIT-46 Architecture and Design

策略: 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 that the compartmentalization serves to allow for and further reinforce privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide when it is appropriate to use and to drop system privileges.

Implementation

策略:

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-2003-0501	Special file system allows attackers to prevent ownership/permission change of certain entries by opening the entries before calling a setuid program.	https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2003-0501
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.	https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2004-0148

Notes

Relationship This can be both primary and resultant. When primary, it can expose a variety of weaknesses because a resource might not have the expected state, and subsequent operations might fail. It is often resultant from Unchecked Error Condition (CWE-391). Maintenance CWE-280 and CWE-274 are too similar. Theoretical 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 software 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). Research Gap This type of issue is under-studied, since researchers often concentrate on whether an object has too many permissions, instead of not enough. These weaknesses are likely to appear in environments with fine-grained models for permissions and privileges, which can include operating systems and other large-scale software packages. However, even highly simplistic permission/privilege models are likely to contain these issues if the developer has not considered the possibility of access failure.

分类映射

映射的分类名	ImNode ID	Mapped Node Name
PLOVER		Fails poorly due to insufficient permissions
WASC	17	Improper Filesystem Permissions
Software Fault Patterns	SFP4	Unchecked Status Condition

VULHUB ™