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

Goal: 1000 CNY · Raised: 1020 CNY

100%
Buy Us a Coffee

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

1001 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-2024-52528 Auth Token can be passed dummy or wrong the middleware response is 200 OK — Gateway 9.8AICriticalAI2024-11-15
CVE-2021-3991 Improper Authorization in dolibarr/dolibarr — dolibarr/dolibarr 4.3AIMediumAI2024-11-15
CVE-2022-31668 User permission validation failure and disclosure of P2P preheat execution logs — Harbor 7.4 High2024-11-14
CVE-2022-31667 Harbor fails to validate the user permissions when updating a robot account — Harbor 6.4 Medium2024-11-14
CVE-2022-31669 Harbor fails to validate the user permissions when updating tag immutability policies — Harbor 6.4 Medium2024-11-14
CVE-2022-31670 Harbor fails to validate the user permissions when updating tag retention policies — Harbor 7.7 High2024-11-14
CVE-2022-31671 Harbor fails to validate the user permissions when reading and updating job execution logs through the P2P preheat execution logs — Harbor 7.4 High2024-11-14
CVE-2022-31666 Harbor fails to validate user permissions while Viewing, updating and deleting Webhook policies — Harbor 7.7 High2024-11-14
CVE-2024-43602 Azure CycleCloud Remote Code Execution Vulnerability — Azure CycleCloud 9.9 Critical2024-11-12
CVE-2024-11073 SourceCodester Hospital Management System delete-account.php improper authorization — Hospital Management System 4.3 Medium2024-11-11
CVE-2024-51525 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.2 Medium2024-11-05
CVE-2024-10598 Tongda OA Annual Leave data.php improper authorization — OA 5.3 Medium2024-10-31
CVE-2024-48921 Kyverno's PolicyException objects can be created in any namespace by default — kyverno 8.1AIHighAI2024-10-29
CVE-2024-9235 Mapster WP Maps <= 1.5.0 - Incorrect Authorization to Authenticated (Contributor+) Arbitrary Options Update — Mapster WP Maps 8.8 High2024-10-25
CVE-2024-9531 MultiVendorX – The Ultimate WooCommerce Multivendor Marketplace Solution <= 4.2.4 - Missing Authorization to Forged Vendor Profile Deletion Email Sending — MultiVendorX – WooCommerce Multivendor Marketplace Solutions 4.3 Medium2024-10-24
CVE-2020-36841 WooCommerce Smart Coupons <= 4.6.0 - Unauthenticated Coupon Creation — WooCommerce Smart Coupons 5.3 Medium2024-10-16
CVE-2024-47876 Sakai: Kernel users created with type roleview can login as a normal user — sakai 8.8 -2024-10-15
CVE-2023-50780 Apache ActiveMQ Artemis: Authenticated users could perform RCE via Jolokia MBeans — Apache ActiveMQ Artemis 8.8AIHighAI2024-10-14
CVE-2024-47084 CORS origin validation is not performed when the request has a cookie in Gradio — gradio 8.1AIHighAI2024-10-10
CVE-2024-47165 CORS origin validation accepts the null origin in Gradio — gradio 6.2AIMediumAI2024-10-10
CVE-2024-38129 Windows Kerberos Elevation of Privilege Vulnerability — Windows Server 2022, 23H2 Edition (Server Core installation) 7.5 High2024-10-08
CVE-2024-38425 Improper Authorization in Performance — Snapdragon 6.1 Medium2024-10-07
CVE-2024-47183 Parse Server's custom object ID allows to acquire role privileges — parse-server 8.1 High2024-10-04
CVE-2024-20441 Cisco Nexus Dashboard Fabric Controller Unauthorized API Endpoint Vulnerability — Cisco Data Center Network Manager 5.7 Medium2024-10-02
CVE-2024-20393 Cisco RV340, RV340W, RV345, and RV345P Dual WAN Gigabit VPN Routers Privilege Escalation Vulnerability — Cisco Small Business RV Series Router Firmware 8.8 High2024-10-02
CVE-2024-9297 SourceCodester Online Railway Reservation System admin improper authorization — Online Railway Reservation System 6.3 Medium2024-09-28
CVE-2024-20414 Cisco IOS XE Software 安全漏洞 — IOS 6.5 Medium2024-09-25
CVE-2024-9082 SourceCodester Online Eyewear Shop User Creation Users.php improper authorization — Online Eyewear Shop 6.3 Medium2024-09-22
CVE-2024-43460 Dynamics 365 Business Central Elevation of Privilege Vulnerability — Dynamics 365 Business Central Online 8.1 High2024-09-17
CVE-2024-6840 Automation-controller: gain access to the k8s api server via job execution with container group 6.6 Medium2024-09-12

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