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

目标: 1000 元 · 已筹: 1325 元

100%
请我们喝杯咖啡

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

CWE-285 授权机制不恰当 类弱点 1059 条 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)
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 properly 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 properly restricted, or by accessing insufficiently-protected, privileged functionality to write the data.
Access ControlGain 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 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) 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 DesignEnsure 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 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-2017-0896 Zulip Server 安全漏洞 — Zulip Server 4.3 -2017-06-02
CVE-2017-7484 PostgreSQL 信息泄露漏洞 — PostgreSQL 7.5 -2017-05-12
CVE-2017-0892 Nextcloud Server 安全漏洞 — Nextcloud Server 6.5 -2017-05-08
CVE-2017-0894 Nextcloud Server 信息泄露漏洞 — Nextcloud Server 5.3 -2017-05-08
CVE-2017-0895 Nextcloud Server 信息泄露漏洞 — Nextcloud Server 4.3 -2017-05-08
CVE-2017-2686 Siemens RUGGEDCOM ROX I 信息泄露漏洞 — RUGGEDCOM ROX I All versions 6.5 -2017-03-29
CVE-2017-2689 Siemens RUGGEDCOM ROX I 安全漏洞 — RUGGEDCOM ROX I All versions 8.8 -2017-03-29
CVE-2016-9464 Nextcloud Server 安全漏洞 — Nextcloud Server Nextcloud Server before 9.0.54 and 10.0.0 4.3 -2017-03-28
CVE-2014-2349 Emerson DeltaV 权限许可和访问控制漏洞 — DeltaV 6.0 -2014-05-22

CWE-285（授权机制不恰当） 是常见的弱点类别，本平台收录该类弱点关联的 1059 条 CVE 漏洞。