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

目标: 1000 元 · 已筹: 1359 元

100%
请我们喝杯咖啡

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

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

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

MITRE CWE 官方描述
CWE：CWE-863 Incorrect Authorization（不正确的授权） 英文：当主体（actor）尝试访问资源或执行操作时，产品会执行授权检查，但未能正确执行该检查。
常见影响 (5)
Confidentiality Read 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.
Integrity Modify 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 Control Gain 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, Availability Execute Unauthorized Code or Commands
An attacker could use elevated privileges to execute unauthorized commands or code.
Availability DoS: 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 Design Divide 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 Design Ensure 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 Design Use 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 Design For 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, Installation Use 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-2024-8011 Logitech Options 安全漏洞 — Options+ 7.1AI High AI 2024-08-25
CVE-2024-38869 ZOHO ManageEngine ServiceDesk Plus和SupportCenter Plus 安全漏洞 — Endpoint Central 8.3 High 2024-08-23
CVE-2024-7836 WordPress plugin Themify Builder 安全漏洞 — Themify Builder 4.3 Medium 2024-08-22
CVE-2024-7604 Logsign Unified SecOps Platform 安全漏洞 — Unified SecOps Platform 7.8AI High AI 2024-08-21
CVE-2024-6337 GitHub Enterprise Server 安全漏洞 — GitHub Enterprise Server 4.3AI Medium AI 2024-08-20
CVE-2024-7711 GitHub Enterprise Server 安全漏洞 — GitHub Enterprise Server 5.3AI Medium AI 2024-08-20
CVE-2024-39690 Capsule 安全漏洞 — capsule 8.5 High 2024-08-20
CVE-2024-43250 WordPress plugin Bit Form Pro 安全漏洞 — Bit Form Pro 7.1 High 2024-08-19
CVE-2024-43131 WordPress plugin Docket 安全漏洞 — Docket (WooCommerce Collections / Wishlist / Watchlist) 7.5 High 2024-08-13
CVE-2024-41941 Siemens SINEC NMS 安全漏洞 — SINEC NMS 4.3 Medium 2024-08-13
CVE-2024-41939 Siemens SINEC NMS 安全漏洞 — SINEC NMS 8.8 High 2024-08-13
CVE-2024-42473 OpenFGA 安全漏洞 — openfga 7.5 High 2024-08-09
CVE-2024-7266 NASK-PIB EZD RP 安全漏洞 — EZD RP 4.3AI Medium AI 2024-08-07
CVE-2024-7265 NASK-PIB EZD RP 安全漏洞 — EZD RP 8.8AI High AI 2024-08-07
CVE-2024-42062 Apache CloudStack 信息泄露漏洞 — Apache CloudStack 7.2AI High AI 2024-08-07
CVE-2024-6358 OpenText ArcSight Intelligence 安全漏洞 — ArcSight Intelligence 6.3 Medium 2024-08-06
CVE-2024-6202 HaloITSM 安全漏洞 — HaloITSM 9.8 Critical 2024-08-06
CVE-2024-6782 Calibre 安全漏洞 — Calibre 9.8 Critical 2024-08-06
CVE-2024-38856 Apache OFBiz 安全漏洞 — Apache OFBiz 5.6AI Medium AI 2024-08-05
CVE-2024-7062 Softvelum Nimble Commander 安全漏洞 — Nimble Commander 8.8 High 2024-07-26
CVE-2024-4447 DotCMS 安全漏洞 — dotCMS core 9.9 Critical 2024-07-26
CVE-2024-5817 GitHub Enterprise Server 安全漏洞 — GitHub Enterprise Server 4.3AI Medium AI 2024-07-16
CVE-2024-5816 GitHub Enterprise Server 安全漏洞 — GitHub Enterprise Server 9.4AI Critical AI 2024-07-16
CVE-2024-39905 Red Discord Bot 安全漏洞 — Red-DiscordBot 5.3 Medium 2024-07-11
CVE-2024-39871 Siemens SINEMA Remote Connect 安全漏洞 — SINEMA Remote Connect Server 6.3 Medium 2024-07-09
CVE-2024-39696 Evmos 安全漏洞 — evmos 8.8 High 2024-07-05
CVE-2024-39322 Aimeos 安全漏洞 — ai-admin-jsonadm 5.5 Medium 2024-07-02
CVE-2024-39352 Synology Camera Firmware 安全漏洞 — Camera Firmware 4.9 Medium 2024-06-28
CVE-2024-6086 lunary 访问控制错误漏洞 — lunary-ai/lunary 4.3AI Medium AI 2024-06-27
CVE-2024-5714 Lunary 访问控制错误漏洞 — lunary-ai/lunary 8.8AI High AI 2024-06-27

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