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

目标: 1000 元 · 已筹: 1359 元

100%

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

CWE-285 授权机制不恰当 类弱点 1311 条 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-2026-33522 ArcGIS Server 安全漏洞 — ArcGIS Server 5.3 Medium 2026-10-26
CVE-2026-116384 Bdtask Garage 24 后端未授权访问漏洞 — Garage 24 Garage Management Software 6.3 Medium 2026-10-26
CVE-2026-116368 DeepSeek Harness Browser 不当授权漏洞 — Harness 7.3 High 2026-10-26
CVE-2026-116274 JIZHICMS 前端订单支付未授权漏洞 — JIZHICMS 4.3 Medium 2026-10-26
CVE-2026-116199 Snipe-IT 8.6.3 前版本 Google SSO 认证绕过漏洞 — snipe-it 8.1 High 2026-10-25
CVE-2026-115477 obsidian-tc 插件拒绝确认可触发 HTTP 破坏性调用 — obsidian-tc 7.1 High 2026-10-23
CVE-2026-57121 PraisonAI Platform API 越权删除漏洞 — PraisonAI 8.1 High 2026-10-23
CVE-2026-114361 HarnessRouter 身份模式应用未授权漏洞 — HarnessRouter 5.6 Medium 2026-10-21
CVE-2026-114249 Insurance-Management-System 更新保单持有人未授权漏洞 — Insurance-Management-System 7.3 High 2026-10-21
CVE-2026-114245 Insurance-Management-System 管理员注册未授权漏洞 — Insurance-Management-System 7.3 High 2026-10-21
CVE-2026-84748 Apache bRPC 远程代码执行漏洞 — Apache bRPC - - 2026-10-21
CVE-2026-81212 DataStage 云包数据不当授权漏洞 — DataStage on Cloud Pak for Data 10.0 Critical 2026-10-20
CVE-2026-112045 donetick 历史删除功能越权漏洞 — donetick 5.4 Medium 2026-10-19
CVE-2026-111913 Admidio 5.0.0 至 5.0.16 授权绕过漏洞 — admidio 4.3 Medium 2026-10-17
CVE-2026-17068 IBM i Network File System 未授权访问漏洞 — i 5.4 Medium 2026-10-16
CVE-2026-17275 IBM i 不当验证漏洞 — i 3.7 Low 2026-10-16
CVE-2026-86009 Mailu 域名管理员跨域邮箱伪造漏洞 — Mailu 8.2 High 2026-10-16
CVE-2026-86008 Mailu 域管理员权限提升漏洞 — Mailu 7.2 High 2026-10-16
CVE-2026-54657 Open Zaak 未基于令牌过滤搜索结果漏洞 — open-zaak 6.5 Medium 2026-10-16
CVE-2026-54683 NL Portal Backend Libraries 3.0.3 任意用户可下载文档漏洞 — nl-portal-backend-libraries 6.5 Medium 2026-10-15
CVE-2026-61838 Lychee ZIP下载相册密码绕过漏洞 — Lychee 8.2 High 2026-10-15
CVE-2026-55383 InvoiceShelf 邮件日志令牌类型混淆致发票泄露 — InvoiceShelf 8.2 High 2026-10-14
CVE-2026-70407 Gitea 组织列表令牌范围绕过漏洞 — Gitea - - 2026-10-14
CVE-2026-109605 Simple Cafe Billing System save_user 权限绕过漏洞 — Simple Cafe Billing System 7.3 High 2026-10-13
CVE-2026-109962 Froxlor 2.3.14 前 MySQLServer 和 Cronjobs API 缺乏授权漏洞 — froxlor 4.3 Medium 2026-10-13
CVE-2026-17475 IBM Planning Analytics Local 安全漏洞 — Planning Analytics 7.1 High 2026-10-12
CVE-2023-54410 Frappe <13.22.0 文档重命名授权绕过漏洞 — frappe 4.3 Medium 2026-10-12
CVE-2026-84314 Nginx UI 用户管理端点缺少安全会话要求导致账户接管漏洞 — nginx-ui 8.7 High 2026-10-12
CVE-2026-108899 Zoraxy improper authorization vulnerability in handleBasicAuth — zoraxy 7.3 High 2026-10-12
CVE-2026-108890 pi-agent-dashboard terminal-handler.ts 权限控制不当漏洞 — pi-agent-dashboard 6.3 Medium 2026-10-12

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