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-2023-22938 Permissions Validation Failure in the ‘sendemail’ REST API Endpoint in Splunk Enterprise — Splunk Enterprise 4.3 Medium2023-02-14
CVE-2023-22931 ‘createrss’ External Search Command Overwrites Existing RSS Feeds in Splunk Enterprise — Splunk Enterprise 4.3 Medium2023-02-14
CVE-2022-34446 Dell PowerPath Management Appliance 安全漏洞 — PowerPath Management Appliance 8.8 High2023-02-10
CVE-2023-21422 SAMSUNG Mobile devices 安全漏洞 — Samsung Mobile Devices 5.7 Medium2023-02-09
CVE-2023-21423 SAMSUNG Mobile devices 安全漏洞 — Samsung Mobile Devices 5.1 Medium2023-02-09
CVE-2023-21424 SAMSUNG Mobile devices 安全漏洞 — Samsung Mobile Devices 5.1 Medium2023-02-09
CVE-2023-21429 SAMSUNG Mobile devices 安全漏洞 — Samsung Mobile Devices 4.0 Medium2023-02-09
CVE-2023-21432 SAMSUNG Mobile devices 安全漏洞 — Smart Things 4.2 Medium2023-02-09
CVE-2023-21433 SAMSUNG Mobile devices 安全漏洞 — Galaxy Store 7.8 High2023-02-09
CVE-2023-21436 SAMSUNG Mobile devices 安全漏洞 — Samsung Mobile Devices 3.3 Low2023-02-09
CVE-2023-21440 SAMSUNG Mobile devices 安全漏洞 — Samsung Mobile Devices 6.2 Medium2023-02-09
CVE-2023-23696 Dell Command Intel vPro Out of Band 安全漏洞 — Dell Command Intel vPro Out of Band (DCIV) 7.0 High2023-02-07
CVE-2022-3229 Rapid7 Metasploit 安全漏洞 — Unified Remote 9.8 -2023-02-06
CVE-2022-24894 Symfony storing cookie headers in HttpCache — symfony 5.9 Medium2023-02-03
CVE-2022-4062 Schneider Electric EcoStruxure Power Commission 授权问题漏洞 — EcoStruxure Power Commission 7.8 High2023-02-01
CVE-2023-0609 Improper Authorization in wallabag/wallabag — wallabag/wallabag--2023-02-01
CVE-2023-0610 Improper Authorization in wallabag/wallabag — wallabag/wallabag--2023-02-01
CVE-2022-34405 Dell Client 安全漏洞 — CPG Drivers 7.3 High2023-01-25
CVE-2023-22480 KubeOperator is vulnerable to unauthorized access to system API — KubeOperator 7.3 High2023-01-14
CVE-2022-4701 Royal Elementor Addons <= 1.3.59 - Insufficient Access Control to Plugin Activation — Royal Addons for Elementor – Addons and Templates Kit for Elementor 4.3 Medium2023-01-10
CVE-2023-21549 Windows SMB Witness Service Elevation of Privilege Vulnerability — Windows 10 Version 1809 8.8 High2023-01-10
CVE-2015-10033 jvvlee MerlinsBoard Grade improper authorization — MerlinsBoard 3.5 Low2023-01-09
CVE-2022-4879 Forged Alliance Forever Vote improper authorization — Forged Alliance Forever 4.6 Medium2023-01-06
CVE-2022-4868 Improper Authorization in froxlor/froxlor — froxlor/froxlor 4.3 -2022-12-31
CVE-2022-4804 Improper Authorization in usememos/memos — usememos/memos 4.3 -2022-12-28
CVE-2022-4688 Improper Authorization in usememos/memos — usememos/memos 5.4 -2022-12-23
CVE-2022-3187 Dataprobe iBoot-PDU 授权问题漏洞 — iBoot-PDU FW 5.3 Medium2022-12-21
CVE-2022-23542 OpenFGA Authorization Bypass — openfga 7.7 High2022-12-20
CVE-2022-2536 Transposh WordPress Translation <= 1.0.9.6 - Authorization Bypass — Transposh WordPress Translation 5.3 Medium2022-12-15
CVE-2022-39902 SAMSUNG Mobile devices 安全漏洞 — Samsung Mobile Devices 6.5 Medium2022-12-08

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