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

Goal: 1000 CNY · Raised: 1310 CNY

100%
Buy Us a Coffee

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

1031 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-3899 Subscription-manager: inadequate authorization of com.redhat.rhsm1 d-bus interface allows local users to modify configuration — Red Hat Enterprise Linux 7 7.8 High2023-08-23
CVE-2023-4243 FULL - Customer <= 2.2.3 - Authenticated(Subscriber+) Improper Authorization to Arbitrary Plugin Installation — FULL – Cliente 8.8 High2023-08-09
CVE-2023-3957 ACF Photo Gallery Field <= 1.9 - Authenticated (Subscriber+) Arbitrary Usermeta Update — ACF Photo Gallery Field 4.3 Medium2023-07-27
CVE-2023-36826 Sentry vulnerable to improper authorization on debug and artifact file downloads — sentry 7.7 High2023-07-25
CVE-2023-23568 Gallagher Command Centre Server 安全漏洞 — Command Centre 4.3 Medium2023-07-25
CVE-2023-25074 Competency access levels not enforced in the server — Command Centre 7.1 High2023-07-24
CVE-2023-22428 Gallagher Command Centre Server 安全漏洞 — Command Centre 7.6 High2023-07-24
CVE-2023-3805 Xiamen Four Letter Video Surveillance Management System Login UserInfoAction.class improper authorization — Video Surveillance Management System 7.3 High2023-07-21
CVE-2023-32482 Dell Wyse Management Suite 授权问题漏洞 — Wyse Management Suite 4.9 Medium2023-07-20
CVE-2023-3574 Improper Authorization in pimcore/customer-data-framework — pimcore/customer-data-framework 7.1 -2023-07-10
CVE-2023-25517 NVIDIA vGPU Software 安全漏洞 — vGPU software 7.1 High2023-07-03
CVE-2023-36611 Ovarro TBox RTUs 授权问题漏洞 — TBox MS-CPU32 6.5 Medium2023-07-03
CVE-2023-34460 Tauri vulnerable to Regression on Filesystem Scope Checks for Dotfiles — tauri 4.8 Medium2023-06-23
CVE-2023-0837 Teamviewer 安全漏洞 — Remote 6.6 Medium2023-06-14
CVE-2023-33142 Microsoft SharePoint Server Elevation of Privilege Vulnerability — Microsoft SharePoint Server 2019 6.5 Medium2023-06-13
CVE-2023-32022 Windows Server Service Security Feature Bypass Vulnerability — Windows Server 2019 7.6 High2023-06-13
CVE-2023-1910 Getwid – Gutenberg Blocks <= 1.8.3 - Improper Authorization via get_remote_templates REST endpoint — Getwid – Gutenberg Blocks 4.3 Medium2023-06-09
CVE-2023-29152 PTC Vuforia Studio Improper Authorization — Vuforia Studio 6.2 Medium2023-06-07
CVE-2023-24476 PTC Vuforia Studio Improper Authorization — Vuforia Studio 1.8 Low2023-06-07
CVE-2020-36729 Slideshow, Image Slider by 2J <= 1.3.31 - Authorization Bypass — Slideshow, Image Slider by 2J 5.4 Medium2023-06-07
CVE-2019-25149 Gallery Images Ape <= 2.0.6 - Authenticated Plugin Deactivation — Gallery Images Ape 7.6 High2023-06-07
CVE-2021-4344 Frontend File Manager <= 18.2 - Privilege Escalation — Frontend File Manager Plugin 6.4 Medium2023-06-07
CVE-2020-36696 Product Input Fields for WooCommerce <= 1.2.6 - Missing Authorization — Product Input Fields for WooCommerce 7.5 High2023-06-07
CVE-2023-30948 Retrieval of Attachments to Comments lacks Authorization — com.palantir.comments:comments 6.5 Medium2023-06-06
CVE-2022-40536 Improper authentication in Modem — Snapdragon 7.5 High2023-06-06
CVE-2022-40521 Improper authorization in Modem — Snapdragon 7.5 High2023-06-06
CVE-2023-0584 VK Blocks <= 1.57.0.5 - Authenticated(Contributor+) Settings Update — VK Blocks 4.3 Medium2023-06-03
CVE-2023-0583 VK Blocks <= 1.57.0.5 - Authenticated(Contributor+) Settings Update — VK Blocks 4.3 Medium2023-06-03
CVE-2023-32709 Low-privileged User can View Hashed Default Splunk Password — Splunk Enterprise 4.3 Medium2023-06-01
CVE-2023-32707 ‘edit_user’ Capability Privilege Escalation — Splunk Enterprise 8.8 High2023-06-01

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