目标达成 感谢每一位支持者 — 我们达成了 100% 目标！

目标: 1000 元 · 已筹: 1310 元

100%
请我们喝杯咖啡

CWE-863 授权机制不正确 类漏洞列表 1383

CWE-863 授权机制不正确 类弱点 1383 条 CVE 漏洞汇总，含 AI 中文分析。

CWE-863属于授权检查缺陷，指系统在验证用户访问权限时未能正确执行检查逻辑。攻击者通常利用此漏洞，通过构造恶意请求或篡改参数，绕过权限控制以访问未授权资源或执行敏感操作。开发者应避免此问题，需确保在关键操作前严格验证用户身份与权限，采用最小权限原则，并实施集中式的授权管理，防止逻辑绕过或硬编码错误。

MITRE CWE 官方描述
CWE：CWE-863 Incorrect Authorization（不正确的授权） 英文：当主体（actor）尝试访问资源或执行操作时，产品会执行授权检查，但未能正确执行该检查。
常见影响 (5)
ConfidentialityRead Application Data, Read Files or Directories
An attacker could bypass intended access restrictions to read sensitive data, either by reading the data directly from a data store that is not correctly restricted, or by accessing insufficiently-protected, privileged functionality to read the data.
IntegrityModify Application Data, Modify Files or Directories
An attacker could bypass intended access restrictions to modify sensitive data, either by writing the data directly to a data store that is not correctly restricted, or by accessing insufficiently-protected, privileged functionality to write the data.
Access ControlGain Privileges or Assume Identity, Bypass Protection Mechanism
An attacker could bypass intended access restrictions to gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
Confidentiality, Integrity, AvailabilityExecute Unauthorized Code or Commands
An attacker could use elevated privileges to execute unauthorized commands or code.
AvailabilityDoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Resource Consumption (Other)
An attacker could gain unauthorized access to resources on the system and excessively consume those resources, leading to a denial of service.
缓解措施 (5)
Architecture and DesignDivide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the …
Architecture and DesignEnsure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible…
Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
Architecture and DesignFor web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests …
System Configuration, InstallationUse the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.
代码示例 (1)
The following code could be for a medical records application. It displays a record to already authenticated users, confirming the user's authorization using a value stored in a cookie.
$role = $_COOKIES['role']; if (!$role) { $role = getRole('user'); if ($role) { // save the cookie to send out in future responses setcookie("role", $role, time()+60*60*2); } else{ ShowLoginScreen(); die("\n"); } } if ($role == 'Reader') { DisplayMedicalHistory($_POST['patient_ID']); } else{ die("You are not Authorized to view this record\n"); }
Bad · PHP
CVE ID标题CVSS风险等级Published
CVE-2021-20188 Podman 访问控制错误漏洞 — podman 7.0 -2021-02-11
CVE-2021-21286 Wwbn Avideo 权限许可和访问控制问题漏洞 — AVideo 7.7 High2021-02-01
CVE-2021-21276 Cydrobolt Polr 安全漏洞 — polr 9.3 Critical2021-02-01
CVE-2020-1725 Red Hat Keycloak 访问控制错误漏洞 — keycloak 5.4 -2021-01-28
CVE-2021-21013 Adobe Bridge 缓冲区错误漏洞 — Magento Commerce 8.1 High2021-01-13
CVE-2021-1144 Cisco Connected Mobile Experiences 访问控制错误漏洞 — Cisco Connected Mobile Experiences 8.8 High2021-01-13
CVE-2021-1143 Cisco Connected Mobile Experiences (CMX) 访问控制错误漏洞 — Cisco Connected Mobile Experiences 4.3 Medium2021-01-13
CVE-2020-26250 JupyterHub Oauthenticator 安全漏洞 — oauthenticator 6.3 Medium2020-12-01
CVE-2020-15248 October CMS 权限许可和访问控制问题漏洞 — october 4.0 Medium2020-11-23
CVE-2020-15246 October CMS 路径遍历漏洞 — october 7.5 High2020-11-23
CVE-2020-28211 Schneider Electric EcoStruxure Control Expert 权限许可和访问控制问题漏洞 — PLC Simulator on EcoStruxureª Control Expert (now Unity Pro) (all versions) 7.8 -2020-11-19
CVE-2020-25699 Moodle 访问控制错误漏洞 — moodle 7.5 -2020-11-19
CVE-2020-26223 Spree 安全漏洞 — spree 7.7 High2020-11-13
CVE-2020-25655 Red Hat Advanced Cluster Management 安全漏洞 — open-cluster-management 5.7 Medium2020-11-09
CVE-2020-24401 Adobe Magento 安全漏洞 — Magento Commerce 6.5 Medium2020-11-09
CVE-2020-15278 Red Discord Bot 安全漏洞 — Red-DiscordBot 7.7 High2020-10-28
CVE-2020-3578 Cisco Firepower Threat Defense和Cisco Adaptive Security Appliances Software 安全漏洞 — Cisco Adaptive Security Appliance (ASA) Software 5.3 Medium2020-10-21
CVE-2020-12503 RocketLinx 输入验证错误漏洞 — P+F Comtrol RocketLinx 7.2 High2020-10-15
CVE-2020-15251 Sopel Channelmgnt 安全漏洞 — sopel-channelmgnt 7.7 High2020-10-13
CVE-2020-3467 Cisco Identity Services Engine 安全漏洞 — Cisco Identity Services Engine Software 8.5 -2020-10-08
CVE-2020-3404 Cisco IOS XE 安全漏洞 — Cisco IOS XE Software 7.8 -2020-09-24
CVE-2020-15163 Python 数据伪造问题漏洞 — tuf 8.7 High2020-09-09
CVE-2020-5418 Cloud Foundry 安全漏洞 — CAPI 4.3 -2020-09-03
CVE-2020-7300 McAfee Data Loss Prevention ePO extension 授权问题漏洞 — DLP ePO extension 4.6 Medium2020-08-12
CVE-2020-15120 I hate money 安全漏洞 — ihatemoney 4.9 Medium2020-07-27
CVE-2020-15126 parser-server 安全漏洞 — parse-server 6.5 Medium2020-07-22
CVE-2020-15110 jupyterhub-kubespawner 安全漏洞 — kubespawner 6.8 Medium2020-07-17
CVE-2020-7499 多款Schneider Electric产品访问控制错误漏洞 — U.motion Servers and Touch Panels (affected versions listed in the security notification) 6.5 -2020-06-16
CVE-2020-11844 多款Micro Focus产品Container Deployment Foundation组件安全漏洞 — Hybrid Cloud Management 10.0 Critical2020-05-29
CVE-2020-6214 SAP S/4HANA 安全漏洞 — SAP S/4HANA (Financial Products Subledger) 6.3 -2020-04-14

CWE-863（授权机制不正确） 是常见的弱点类别，本平台收录该类弱点关联的 1383 条 CVE 漏洞。