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

目标: 1000 元 · 已筹: 1000 元

100.0%
请我们喝杯咖啡

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

CWE-863 授权机制不正确 类弱点 1279 条 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-2023-22251 Adobe Commerce 安全漏洞 — Magento Commerce 4.3 Medium2023-03-27
CVE-2023-25017 RIFARTEK IOT Wall 安全漏洞 — IOT Wall 8.1 High2023-03-27
CVE-2023-25923 IBM Security Guardium 安全漏洞 — Security Key Lifecycle Manager 2.7 Low2023-03-21
CVE-2023-25924 IBM Security Guardium 安全漏洞 — Security Key Lifecycle Manager 5.4 Medium2023-03-21
CVE-2023-26484 KubeVirt 安全漏洞 — kubevirt 8.2 High2023-03-15
CVE-2022-39214 Combodo iTop 安全漏洞 — iTop 9.6 Critical2023-03-14
CVE-2023-24999 HashiCorp Vault 安全漏洞 — Vault 4.4 Medium2023-03-10
CVE-2023-27486 xCAT 安全漏洞 — xcat-core 8.1 High2023-03-08
CVE-2023-27485 Feedbacksystem 安全漏洞 — feedbacksystem 4.3 Medium2023-03-07
CVE-2023-26056 XWiki Platform 安全漏洞 — xwiki-platform 5.4 Medium2023-03-02
CVE-2023-23947 ArgoCD 安全漏洞 — argo-cd 9.1 Critical2023-02-16
CVE-2023-25173 containerd 安全漏洞 — containerd 5.3 Medium2023-02-16
CVE-2022-34397 Dell EMC Unisphere for PowerMax 安全漏洞 — Unisphere for PowerMax 6.9 Medium2023-02-13
CVE-2023-24829 Apache IoTDB 安全漏洞 — Apache IoTDB Workbench 8.8 -2023-01-31
CVE-2022-45435 IdentityIQ 安全漏洞 — IdentityIQ 6.8 Medium2023-01-31
CVE-2023-22610 EcoStruxure Geo SCADA Expert 安全漏洞 — EcoStruxure Geo SCADA Expert 2019 - 2021 (formerly known as ClearSCADA) 9.1 Critical2023-01-31
CVE-2023-22482 Argo CD 安全漏洞 — argo-cd 9.1 Critical2023-01-25
CVE-2023-22500 GLPI 安全漏洞 — glpi 7.5 High2023-01-25
CVE-2022-23739 GitHub Enterprise Server 安全漏洞 — GitHub Enterprise Server 7.8 -2023-01-17
CVE-2022-45353 WordPress plugin Betheme theme 安全漏洞 — Betheme 4.3 Medium2023-01-14
CVE-2023-0298 firefly-iii 授权问题漏洞 — firefly-iii/firefly-iii 7.1 -2023-01-14
CVE-2022-2155 Hitachi Energy Lumada APM 安全漏洞 — Lumada APM 5.7 Medium2023-01-12
CVE-2022-46258 GitHub Enterprise Server 安全漏洞 — GitHub Enterprise Server 6.5 -2023-01-09
CVE-2022-43438 EasyTest 安全漏洞 — EasyTest 8.8 High2023-01-03
CVE-2022-23553 Alpine 安全漏洞 — alpine 7.5 High2022-12-28
CVE-2020-36625 destiny.gg chat 跨站请求伪造漏洞 — chat 4.3 Medium2022-12-22
CVE-2022-3188 Dataprobe iBoot-PDU 访问控制错误漏洞 — iBoot-PDU FW 5.3 Medium2022-12-21
CVE-2020-36622 Bienlein 跨站请求伪造漏洞 — bienlein 4.3 Medium2022-12-21
CVE-2020-36623 Bienlein 跨站请求伪造漏洞 — Pengu 4.3 Medium2022-12-21
CVE-2021-4268 phpRedisAdmin 跨站请求伪造漏洞 — phpRedisAdmin 4.3 Medium2022-12-21

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