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

目标: 1000 元 · 已筹: 1336

100%

CWE-285 授权机制不恰当 类漏洞列表 1213

CWE-285 授权机制不恰当 类弱点 1213 条 CVE 漏洞汇总,含 AI 中文分析。

CWE-285 属于权限控制缺陷,指系统在访问资源或执行操作时未正确执行授权检查。攻击者常通过篡改请求参数或绕过前端限制,以非授权身份访问敏感数据或执行特权操作。开发者应实施严格的基于角色的访问控制,在服务器端对所有请求进行细粒度权限验证,确保仅允许合法用户执行相应操作,从而杜绝越权风险。

MITRE CWE 官方描述
CWE:CWE-285 Improper Authorization 英文:The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
常见影响 (3)
Confidentiality Read 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 properly restricted, or by accessing insufficiently-protected, privileged functionality to read the data.
Integrity Modify 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 properly restricted, or by accessing insufficiently-protected, privileged functionality to write the data.
Access Control Gain Privileges or Assume Identity, Execute Unauthorized Code or Commands
When access control checks are not applied consistently - or not at all - an attacker could gain privileges and execute unauthorized code or commands by modifying or reading critical data directly, or by accessing insufficiently-protected, privileged functionality.
缓解措施 (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) 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 same role.
Architecture and Design Ensure that you perform access control checks related to your business logic. These checks may be different than the access control checks that you apply 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 to…
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.
代码示例 (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-2025-6525 70mai 1S 安全漏洞 — 1S 4.3 Medium 2025-06-23
CVE-2025-6099 szluyu99 gin-vue-blog 安全漏洞 — gin-vue-blog 5.3 Medium 2025-06-16
CVE-2025-46840 Adobe Experience Manager 授权问题漏洞 — Adobe Experience Manager 8.7 High 2025-06-10
CVE-2024-43706 Elastic Kibana 安全漏洞 — Kibana 7.6 High 2025-06-10
CVE-2025-43585 Adobe Commerce 授权问题漏洞 — Adobe Commerce 8.2 High 2025-06-10
CVE-2025-5522 bskms 安全漏洞 — bskms 蓝天幼儿园管理系统 7.3 High 2025-06-03
CVE-2025-5511 shiyi-blog 安全漏洞 — shiyi-blog 5.3 Medium 2025-06-03
CVE-2025-3454 Grafana 安全漏洞 — Grafana 5.0 Medium 2025-06-02
CVE-2025-4631 WordPress plugin Profitori 授权问题漏洞 — The E-Commerce ERP: Purchasing, Inventory, Fulfillment, Manufacturing, BOM, Accounting, Sales Analysis 9.8 Critical 2025-05-31
CVE-2025-4672 WordPress plugin Offsprout Page Builder 授权问题漏洞 — Offsprout Page Builder 8.8 High 2025-05-31
CVE-2025-4103 WordPress plugin WP-GeoMeta 授权问题漏洞 — WP-GeoMeta 8.8 High 2025-05-31
CVE-2025-5175 pypickle 安全漏洞 — pypickle 5.3 Medium 2025-05-26
CVE-2025-48371 OpenFGA 授权问题漏洞 — openfga 9.8AI Critical AI 2025-05-22
CVE-2025-48063 XWiki Platform 安全漏洞 — xwiki-platform 7.1AI High AI 2025-05-21
CVE-2025-4819 RuoYi 安全漏洞 — RuoYi 3.1 Low 2025-05-17
CVE-2025-4474 WordPress plugin Frontend Dashboard 授权问题漏洞 — Frontend Dashboard 8.8 High 2025-05-13
CVE-2025-4473 WordPress plugin Frontend Dashboard 授权问题漏洞 — Frontend Dashboard 8.8 High 2025-05-13
CVE-2025-29827 Microsoft Azure Automation 授权问题漏洞 — Azure Automation 9.9 Critical 2025-05-08
CVE-2025-4104 WordPress plugin Frontend Dashboard 授权问题漏洞 — Frontend Dashboard 9.8 Critical 2025-05-07
CVE-2025-3921 WordPress plugin PeproDev Ultimate Profile Solutions 授权问题漏洞 — PeproDev Ultimate Profile Solutions 8.2 High 2025-05-07
CVE-2025-3924 WordPress plugin PeproDev Ultimate Profile Solutions 授权问题漏洞 — PeproDev Ultimate Profile Solutions 5.3 Medium 2025-05-07
CVE-2025-3918 WordPress plugin Job Listings 授权问题漏洞 — Job Listings 9.8 Critical 2025-05-03
CVE-2025-4136 Weitong Mall 安全漏洞 — Mall 5.4 Medium 2025-04-30
CVE-2025-30392 Microsoft Azure Bot Framework SDK 授权问题漏洞 — Azure AI Bot Service 9.8 Critical 2025-04-30
CVE-2025-30390 Microsoft Azure 授权问题漏洞 — Azure Machine Learning 9.9 Critical 2025-04-30
CVE-2025-30389 Microsoft Azure Bot Framework SDK 授权问题漏洞 — Azure AI Bot Service 8.7 High 2025-04-30
CVE-2025-32972 XWiki Platform 安全漏洞 — xwiki-platform 2.7 Low 2025-04-30
CVE-2025-4017 Novel-Plus 安全漏洞 — Novel-Plus 4.3 Medium 2025-04-28
CVE-2025-4016 Novel-Plus 安全漏洞 — Novel-Plus 5.4 Medium 2025-04-28
CVE-2025-3981 wowjoy Internet Doctor Workstation System 安全漏洞 — Internet Doctor Workstation System 4.3 Medium 2025-04-27

CWE-285(授权机制不恰当) 是常见的弱点类别,本平台收录该类弱点关联的 1213 条 CVE 漏洞。