目标达成 感谢每一位支持者 — 我们达成了 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-2023-6837 WSO2 API Manager 安全漏洞 — WSO2 API Manager 8.5 High 2023-12-15
CVE-2023-45185 IBM i 代码问题漏洞 — i Access Client Solutions 7.4 High 2023-12-14
CVE-2023-49273 Umbraco 安全漏洞 — Umbraco-CMS 5.4 Medium 2023-12-12
CVE-2023-48227 Umbraco 安全漏洞 — Umbraco-CMS 4.3 Medium 2023-12-12
CVE-2023-6542 SAP Emarsys SDK 安全漏洞 — SAP EMARSYS SDK ANDROID 7.1 High 2023-12-12
CVE-2023-3443 GitLab 安全漏洞 — GitLab 3.1 Low 2023-12-01
CVE-2023-3964 GitLab 安全漏洞 — GitLab 4.3 Medium 2023-12-01
CVE-2023-4317 GitLab 安全漏洞 — GitLab 4.3 Medium 2023-12-01
CVE-2023-4658 GitLab 安全漏洞 — GitLab 3.1 Low 2023-12-01
CVE-2023-5995 GitLab 安全漏洞 — GitLab 4.4 Medium 2023-12-01
CVE-2023-47827 WordPress Plugin Events Addon for Elementor 安全漏洞 — Events Addon for Elementor 6.5 Medium 2023-11-30
CVE-2023-40610 Apache Superset 安全漏洞 — Apache Superset 6.3 Medium 2023-11-27
CVE-2023-48712 Warpgate 安全漏洞 — warpgate 7.1 High 2023-11-24
CVE-2023-5553 AXIS OS 安全漏洞 — AXIS OS 7.6 High 2023-11-21
CVE-2023-48218 Strapi 安全漏洞 — strapi-plugin-protected-populate 5.3 Medium 2023-11-20
CVE-2023-3379 WAGO PFC100 安全漏洞 — Compact Controller 100 (751-9301) 5.3 Medium 2023-11-20
CVE-2022-40681 Fortinet FortiClient 安全漏洞 — FortiClientWindows 7.1 High 2023-11-14
CVE-2023-31403 SAP Business One 访问控制错误漏洞 — SAP Business One 9.6 Critical 2023-11-14
CVE-2023-47037 Apache Airflow 安全漏洞 — Apache Airflow 5.4 - 2023-11-12
CVE-2023-4379 GitLab Enterprise Edition 安全漏洞 — GitLab 8.1 High 2023-11-09
CVE-2023-46244 XWiki Platform 安全漏洞 — xwiki-platform 9.1 Critical 2023-11-07
CVE-2023-46139 KernelSU 安全漏洞 — KernelSU 5.0 Medium 2023-10-30
CVE-2023-38218 Adobe Commerce 安全漏洞 — Adobe Commerce 8.8 High 2023-10-13
CVE-2023-41882 vantage6 代码问题漏洞 — vantage6 5.4 Medium 2023-10-11
CVE-2023-28635 vantage6 代码问题漏洞 — vantage6 5.4 Medium 2023-10-11
CVE-2023-5521 kernelsu 安全漏洞 — tiann/kernelsu 8.3 - 2023-10-11
CVE-2023-36556 Fortinet FortiMail 安全漏洞 — FortiMail 8.6 High 2023-10-10
CVE-2022-3248 Kubernetes 安全漏洞 — kubernetes 4.4 Medium 2023-10-05
CVE-2023-4997 ProIntegra Uptime DC 安全漏洞 — UptimeDC 8.8 High 2023-10-04
CVE-2023-5106 GitLab Enterprise Edition 安全漏洞 — GitLab 8.2 High 2023-10-02

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