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

目标: 1000 元 · 已筹: 1336

100%

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

CWE-863 授权机制不正确 类弱点 2077 条 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-27309 Apache Kafka 安全漏洞 — Apache Kafka 4.4 - 2024-04-12
CVE-2024-1740 lunary 安全漏洞 — lunary-ai/lunary 7.1AI High AI 2024-04-10
CVE-2024-1741 lunary 授权问题漏洞 — lunary-ai/lunary 8.8AI High AI 2024-04-10
CVE-2024-29834 Apache Pulsar 安全漏洞 — Apache Pulsar 6.4 Medium 2024-04-02
CVE-2024-31134 JetBrains TeamCity 安全漏洞 — TeamCity 6.5 Medium 2024-03-28
CVE-2024-29892 ZITADEL 安全漏洞 — zitadel 6.1 Medium 2024-03-27
CVE-2024-23451 Elasticsearch 安全漏洞 — Elasticsearch 4.4 Medium 2024-03-27
CVE-2023-6400 Micro Focus ZENworks Configuration Management 安全漏洞 — ZENworks Configuration Management (ZCM) 7.4 High 2024-03-27
CVE-2024-27105 Frappe 安全漏洞 — frappe 8.1 High 2024-03-20
CVE-2024-22412 ClickHouse 安全漏洞 — ClickHouse 2.4 Low 2024-03-18
CVE-2024-1479 WordPress Plugin WP Show Posts 安全漏洞 — WP Show Posts 5.3 Medium 2024-03-13
CVE-2024-1452 WordPress Plugin GenerateBlocks 安全漏洞 — GenerateBlocks 4.3 Medium 2024-03-13
CVE-2024-28098 Apache Pulsar 安全漏洞 — Apache Pulsar 6.4 Medium 2024-03-12
CVE-2023-45793 Siemens Siveillance Control 安全漏洞 — Siveillance Control 5.5 Medium 2024-03-12
CVE-2024-22133 SAP Fiori 安全漏洞 — SAP Fiori Front End Server 4.6 Medium 2024-03-12
CVE-2024-28229 JetBrains YouTrack 安全漏洞 — YouTrack 6.5 Medium 2024-03-07
CVE-2024-0199 GitLab 安全漏洞 — GitLab 7.7 High 2024-03-07
CVE-2024-27933 Deno 安全漏洞 — deno 8.3 High 2024-03-06
CVE-2024-27915 Sulu 安全漏洞 — sulu 6.8 Medium 2024-03-06
CVE-2024-27288 1Panel 安全漏洞 — 1Panel 6.3 Medium 2024-03-06
CVE-2024-24761 Galette 安全漏洞 — galette 7.5 High 2024-03-06
CVE-2024-28174 JetBrains TeamCity 安全漏洞 — TeamCity 5.8 Medium 2024-03-06
CVE-2024-27138 Apache Archiva 安全漏洞 — Apache Archiva 7.5 - 2024-03-01
CVE-2024-27139 Apache Archiva 安全漏洞 — Apache Archiva 9.1 - 2024-03-01
CVE-2023-47716 IBM FileNet Content Manager 权限许可和访问控制问题漏洞 — Filenet Content Manager 6.3 Medium 2024-03-01
CVE-2024-26016 Apache Superset 安全漏洞 — Apache Superset 4.3 Medium 2024-02-28
CVE-2024-24779 Apache Superset 安全漏洞 — Apache Superset 5.0 Medium 2024-02-28
CVE-2024-24773 Apache Superset 安全漏洞 — Apache Superset 4.9 Medium 2024-02-28
CVE-2023-3509 GitLab 访问控制错误漏洞 — GitLab 3.7 Low 2024-02-21
CVE-2024-26145 Discourse 安全漏洞 — discourse-calendar 6.5 Medium 2024-02-21

CWE-863(授权机制不正确) 是常见的弱点类别,本平台收录该类弱点关联的 2077 条 CVE 漏洞。