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

目标: 1000 元 · 已筹: 1310

100%

CWE-862 授权机制缺失 类漏洞列表 5782

CWE-862 授权机制缺失 类弱点 5782 条 CVE 漏洞汇总,含 AI 中文分析。

CWE-862 属于缺失授权漏洞,指产品在用户访问资源或执行操作时未进行权限校验。攻击者通常通过直接修改请求参数或构造恶意 URL,绕过前端限制以访问未授权数据或执行敏感操作。开发者应避免仅依赖前端验证,需在服务端对每个请求实施严格的身份认证与权限检查,确保用户仅能访问其被授权的资源,从而从根本上消除越权风险。

MITRE CWE 官方描述
CWE:CWE-862 Missing Authorization(缺失授权) 英文:当主体尝试访问资源或执行操作时,产品未执行授权检查。
常见影响 (4)
ConfidentialityRead Application Data, Read Files or Directories
An attacker could read sensitive data, either by reading the data directly from a data store that is not restricted, or by accessing insufficiently-protected, privileged functionality to read the data.
IntegrityModify Application Data, Modify Files or Directories
An attacker could modify sensitive data, either by writing the data directly to a data store that is not restricted, or by accessing insufficiently-protected, privileged functionality to write the data.
Access ControlGain Privileges or Assume Identity, Bypass Protection Mechanism
An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
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.
代码示例 (2)
This function runs an arbitrary SQL query on a given database, returning the result of the query.
function runEmployeeQuery($dbName, $name){ mysql_select_db($dbName,$globalDbHandle) or die("Could not open Database".$dbName); //Use a prepared statement to avoid CWE-89 $preparedStatement = $globalDbHandle->prepare('SELECT * FROM employees WHERE name = :name'); $preparedStatement->execute(array(':name' => $name)); return $preparedStatement->fetchAll(); } /.../ $employeeRecord = runEmployeeQuery('EmployeeDB',$_GET['EmployeeName']);
Bad · PHP
The following program could be part of a bulletin board system that allows users to send private messages to each other. This program intends to authenticate the user before deciding whether a private message should be displayed. Assume that LookupMessageObject() ensures that the $id argument is numeric, constructs a filename based on that id, and reads the message details from that file. Also ass…
sub DisplayPrivateMessage { my($id) = @_; my $Message = LookupMessageObject($id); print "From: " . encodeHTML($Message->{from}) . "<br>\n"; print "Subject: " . encodeHTML($Message->{subject}) . "\n"; print "<hr>\n"; print "Body: " . encodeHTML($Message->{body}) . "\n"; } my $q = new CGI; # For purposes of this example, assume that CWE-309 and # CWE-523 do not apply. if (! AuthenticateUser($q->param('username'), $q->param('password'))) { ExitError("invalid username or password"); } my $id = $q->param('id'); DisplayPrivateMessage($id);
Bad · Perl
CVE ID标题CVSS风险等级Published
CVE-2021-25014 WordPress plugin 跨站脚本漏洞 — Ibtana – WordPress Website Builder 3.5 -2022-02-14
CVE-2022-22535 SAP ERP HCM 安全漏洞 — SAP ERP HCM (Portugal)--2022-02-09
CVE-2022-24317 Schneider Electric Interactive Graphical SCADA System 安全漏洞 — Interactive Graphical SCADA System Data Server (V15.0.0.22020 and prior) 7.5 -2022-02-09
CVE-2022-23621 XWiki Platform 安全漏洞 — xwiki-platform 5.5 Medium2022-02-09
CVE-2022-23617 XWiki Platform 安全漏洞 — xwiki-platform 6.5 Medium2022-02-09
CVE-2022-21660 Gin-Vue-Admin 权限许可和访问控制问题漏洞 — gin-vue-admin 8.1 High2022-02-09
CVE-2021-25084 WordPress plugin 访问控制错误漏洞 — Advanced Cron Manager 4.3 -2022-02-07
CVE-2021-24993 Wordpress Plugin Ultimate Product Catalog 跨站请求伪造漏洞 — Ultimate Product Catalog – WordPress Catalog Plugin 4.3 -2022-02-07
CVE-2021-24839 WordPress plugin 跨站请求伪造漏洞 — SupportCandy – Helpdesk & Support Ticket System 7.5 -2022-02-07
CVE-2022-0218 WordPress plugin 跨站脚本漏洞 — WP HTML Mail 8.3 High2022-02-04
CVE-2021-25093 WordPress 安全漏洞 — Link Library 7.5 -2022-02-01
CVE-2021-44795 Kron Single Connect 安全漏洞 — Single Connect 5.3 Medium2022-01-27
CVE-2021-44794 Kron Single Connect 安全漏洞 — Single Connect 5.3 Medium2022-01-27
CVE-2021-44793 Kron Single Connect 安全漏洞 — Single Connect 8.6 High2022-01-27
CVE-2021-44792 Kron Single Connect 安全漏洞 — Single Connect 5.3 Medium2022-01-27
CVE-2022-23945 Apache ShenYu 访问控制错误漏洞 — Apache ShenYu (incubating) 9.1 -2022-01-25
CVE-2022-23944 Apache ShenYu 访问控制错误漏洞 — Apache ShenYu (incubating) 9.1 -2022-01-25
CVE-2021-25013 WordPress 跨站请求伪造漏洞 — Qubely – Advanced Gutenberg Blocks 6.5 -2022-01-24
CVE-2021-24968 WordPress 跨站请求伪造漏洞 — Ultimate FAQ – WordPress FAQ and Accordion Plugin 3.5 -2022-01-24
CVE-2021-24906 WordPress plugin 访问控制错误漏洞 — Protect WP Admin 7.5 -2022-01-24
CVE-2022-0236 WordPress 安全漏洞 — WP Import Export 7.5 High2022-01-18
CVE-2022-0178 Snipe-IT 访问控制错误漏洞 — snipe/snipe-it 6.3 Medium2022-01-13
CVE-2022-0179 Snipe-IT 安全漏洞 — snipe/snipe-it 5.4 -2022-01-12
CVE-2022-22111 DayByDay CRM 授权问题漏洞 — DaybydayCRM 8.8 High2022-01-05
CVE-2022-22108 Daybyday CRM 授权问题漏洞 — DaybydayCRM 4.3 Medium2022-01-05
CVE-2022-22107 Daybyday CRM 授权问题漏洞 — DaybydayCRM 4.3 Medium2022-01-05
CVE-2021-24831 WordPress 安全漏洞 — Tab – Accordion, FAQ 7.5 -2022-01-03
CVE-2021-24997 WordPress 插件安全漏洞 — WP Guppy 6.5 -2021-12-27
CVE-2021-40853 TCMAN GIM 安全漏洞 — GIM 7.2 High2021-12-17
CVE-2021-27859 FatPipe 安全漏洞 — WARP 8.8 High2021-12-15

CWE-862(授权机制缺失) 是常见的弱点类别,本平台收录该类弱点关联的 5782 条 CVE 漏洞。