名称: Authorization Bypass Through User-Controlled Key

The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

基本信息

引入方式

Architecture and Design : REALIZATION: This weakness is caused during implementation of an architectural security tactic.
Architecture and Design
Implementation

适用平台

编程语言

类： Not Language-Specific (Undetermined)

常见后果

影响范围	影响	可能性
Access Control	Bypass Protection Mechanism 注意： Access control checks for specific user data or functionality can be bypassed.
Access Control	Gain Privileges or Assume Identity 注意： Horizontal escalation of privilege is possible (one user can view/modify information of another user).
Access Control	Gain Privileges or Assume Identity 注意： Vertical escalation of privilege is possible if the user-controlled key is actually a flag that indicates administrator status, allowing the attacker to gain administrative access.

观察示例

参考资料	描述
CVE-2021-36539	An educational application does not appropriately restrict file IDs to a particular user. The attacker can brute-force guess IDs, indicating IDOR.

潜在缓解措施

Phases : Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Phases : Architecture and Design // Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Phases : Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.

检测方法

Automated Static Analysis

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.)
有效性 : High

漏洞映射说明

依据 : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
备注 : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

备注

As of CWE 4.20, the relationship between IDOR and BOLA needs to be investigated more closely, including research into how these terms are used in the industry. The CWE team suspects that IDOR can be a part of BOLA, but BOLA expands on the weakness inherent to IDOR in that it is not only about objects that are being directly referenced.

参考资料

提交记录

名称	组织	日期	发布日期	Version
Evgeny Lebanidze	Cigital	2008-01-30 +00:00	2008-01-30 +00:00	Draft 8

修改记录

名称	组织	日期	备注
CWE Content Team	MITRE	2008-09-08 +00:00	updated Common_Consequences, Relationships, Type
CWE Content Team	MITRE	2008-10-14 +00:00	updated Description
CWE Content Team	MITRE	2009-03-10 +00:00	updated Relationships
CWE Content Team	MITRE	2009-05-27 +00:00	updated Relationships
CWE Content Team	MITRE	2009-10-29 +00:00	updated Common_Consequences
CWE Content Team	MITRE	2010-06-21 +00:00	updated Relationships
CWE Content Team	MITRE	2011-03-29 +00:00	updated Alternate_Terms, Applicable_Platforms, Description, Name, Potential_Mitigations, Relationships
CWE Content Team	MITRE	2011-06-01 +00:00	updated Common_Consequences, Relationships
CWE Content Team	MITRE	2012-05-11 +00:00	updated Relationships
CWE Content Team	MITRE	2013-02-21 +00:00	updated Alternate_Terms, Common_Consequences
CWE Content Team	MITRE	2013-07-17 +00:00	updated Relationships
CWE Content Team	MITRE	2014-07-30 +00:00	updated Relationships
CWE Content Team	MITRE	2017-11-08 +00:00	updated Description, Enabling_Factors_for_Exploitation, Modes_of_Introduction, Relationships
CWE Content Team	MITRE	2018-03-27 +00:00	updated Relationships
CWE Content Team	MITRE	2019-06-20 +00:00	updated Relationships
CWE Content Team	MITRE	2020-02-24 +00:00	updated Relationships
CWE Content Team	MITRE	2020-06-25 +00:00	updated Alternate_Terms
CWE Content Team	MITRE	2020-12-10 +00:00	updated Relationships
CWE Content Team	MITRE	2021-03-15 +00:00	updated Alternate_Terms
CWE Content Team	MITRE	2021-10-28 +00:00	updated Relationships
CWE Content Team	MITRE	2023-04-27 +00:00	updated Detection_Factors, Relationships
CWE Content Team	MITRE	2023-06-29 +00:00	updated Mapping_Notes
CWE Content Team	MITRE	2023-10-26 +00:00	updated Observed_Examples
CWE Content Team	MITRE	2024-02-29 +00:00	updated Demonstrative_Examples
CWE Content Team	MITRE	2025-12-11 +00:00	updated References, Relationships, Weakness_Ordinalities
CWE Content Team	MITRE	2026-04-30 +00:00	updated Alternate_Terms, Maintenance_Notes, References
CWE Content Team	MITRE	2026-10-28 +00:00	updated Description, Modes_of_Introduction, Time_of_Introduction

CWE-639 详情

CWE-639