Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

CWE-285 (授权机制不恰当) — Vulnerability Class 986

986 vulnerabilities classified as CWE-285 (授权机制不恰当). AI Chinese analysis included.

CWE-285 represents a critical access control weakness where an application fails to verify whether a user possesses the necessary permissions to access a specific resource or execute a particular action. Attackers typically exploit this vulnerability by manipulating request parameters, such as changing user IDs in URLs or API calls, to bypass security checks and access data belonging to other users or perform administrative tasks. This often leads to severe data breaches or unauthorized system modifications. To prevent such flaws, developers must implement robust, centralized authorization mechanisms that consistently validate user privileges for every sensitive operation. Relying solely on client-side checks is insufficient; instead, server-side enforcement using role-based or attribute-based access control ensures that only authenticated and authorized entities can interact with protected resources, thereby maintaining strict integrity and confidentiality.

MITRE CWE Description
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
Common Consequences (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.
Mitigations (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.
Examples (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 IDTitleCVSSSeverityPublished
CVE-2021-39341 OptinMonster <= 2.6.4 Unprotected REST-API Endpoints — OptinMonster 8.2 High2021-11-01
CVE-2021-41313 Atlassian Jira 安全漏洞 — Jira Server 4.3 -2021-11-01
CVE-2021-41308 Atlassian Jira 安全漏洞 — Jira Server 6.5 -2021-10-26
CVE-2021-31384 Junos OS: SRX Series: Under a specific device configuration an attacker can access the devices J-Web management services from any interface, regardless of security settings protecting the service — Junos OS 7.2 High2021-10-19
CVE-2021-38486 InHand Networks IR615 Router — IR615 Router 8.0 High2021-10-19
CVE-2021-42336 Huachu Digital Technology Co.,Ltd. Easytest - Improper Authorization — Easytest 4.3 Medium2021-10-15
CVE-2021-42332 ShinHer Information Co., LTD. ShinHer StudyOnline System - Improper Authorization-3 — ShinHer StudyOnline System 4.3 Medium2021-10-15
CVE-2021-42331 ShinHer Information Co., LTD. ShinHer StudyOnline System - Improper Authorization-2 — ShinHer StudyOnline System 5.4 Medium2021-10-15
CVE-2021-42330 ShinHer Information Co., LTD. ShinHer StudyOnline System - Improper Authorization-1 — ShinHer StudyOnline System 8.8 High2021-10-15
CVE-2021-41137 Bypassing policy restrictions on regular users — minio 8.8 High2021-10-13
CVE-2021-33723 Siemens SINEC NMS 安全漏洞 — SINEC NMS 6.5 -2021-10-12
CVE-2021-39317 AccessPress Themes - Authenticated Malicious File Upload — Access Demo Importer 8.8 High2021-10-11
CVE-2021-41976 Tad Uploader - Improper Authorization — Uploader 5.3 Medium2021-10-08
CVE-2021-41975 Tad TadTools - Improper Authorization — TadTools 7.5 High2021-10-08
CVE-2021-41974 Tad Book3 - Improper Authorization — Tad Book3 9.1 Critical2021-10-08
CVE-2021-41568 Tad Web - Improper Authorization — Tad Web 5.3 Medium2021-10-08
CVE-2021-41564 Tad Honor - Improper Authorization — Tad Honor 5.3 Medium2021-10-08
CVE-2021-25499 Samsung Galaxy Store 授权问题漏洞 — Galaxy Store 7.1 High2021-10-06
CVE-2021-41100 Account takeover when having only access to a user's short lived token in wire-server — wire-server 7.4 High2021-10-04
CVE-2021-41093 Account takeover when having only access to a user's short lived token — wire-ios 7.4 High2021-10-04
CVE-2021-25460 SAMSUNG SMR 安全漏洞 — Samsung Mobile Devices 4.0 Medium2021-09-09
CVE-2021-25459 SAMSUNG SMR 安全漏洞 — Samsung Mobile Devices 4.0 Medium2021-09-09
CVE-2021-3049 Cortex XSOAR: Improper Authorization of Incident Investigations Vulnerability — Cortex XSOAR 2.6 Low2021-09-08
CVE-2021-28567 Magento Commerce improper authorization allows an authenticated user to perform certain functions without permission — Magento Commerce 6.5 -2021-09-08
CVE-2021-36029 Magento Commerce Improper Authorization Vulnerability Could Lead To Remote Code Execution — Magento Commerce 9.1 Critical2021-09-01
CVE-2021-36037 Magento Commerce Improper Authorization Vulnerability Could Lead To Information Exposure — Magento Commerce 6.5 Medium2021-09-01
CVE-2021-27663 CEM Systems AC2000 — CEM Systems AC2000 8.2 High2021-08-30
CVE-2021-34434 Eclipse Mosquitto 授权问题漏洞 — Eclipse Mosquitto 4.3 -2021-08-30
CVE-2021-28626 Adobe Experience Manager Improper Authorization at /content/usergenerated — Experience Manager 3.7 Low2021-08-24
CVE-2021-3616 Lenovo Smart Camera 安全漏洞 — Smart Camera X3, X5, and C2E firmware 9.4 Critical2021-08-17

Vulnerabilities classified as CWE-285 (授权机制不恰当) represent 986 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.