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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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-2019-10159 cfme-gemset 授权问题漏洞 — cfme 4.3 -2019-06-14
CVE-2019-6581 Siemens Siveillance VMS 权限许可和访问控制问题漏洞 — Siveillance VMS 2017 R2 9.8 -2019-06-12
CVE-2019-6582 Siemens Siveillance VMS 权限许可和访问控制问题漏洞 — Siveillance VMS 2017 R2 8.2 -2019-06-12
CVE-2019-1842 Cisco IOS XR Software Secure Shell Authentication Vulnerability — Cisco IOS XR Software 5.4 -2019-06-05
CVE-2019-1851 Cisco Identity Services Engine Arbitrary Client Certificate Creation Vulnerability — Cisco Identity Services Engine Software 6.8 -2019-05-16
CVE-2019-1859 Cisco Small Business Switches Secure Shell Certificate Authentication Bypass Vulnerability — Cisco Small Business 200 Series Smart Switches 9.8 -2019-05-03
CVE-2019-3842 systemd 授权问题漏洞 — systemd 7.0 -2019-04-09
CVE-2019-3849 Moodle 权限许可和访问控制问题漏洞 — moodle 8.8 -2019-03-26
CVE-2015-3954 多款Hospira产品安全漏洞 — Plum A+ Infusion System 9.8 -2019-03-25
CVE-2019-3785 Cloud Controller provides signed URL with write authorization to read only user — CAPI 8.1 -2019-03-13
CVE-2019-1603 Cisco NX-OS Software Privilege Escalation Vulnerability — Nexus 3000 Series Switches 7.8 -2019-03-08
CVE-2019-1604 Cisco NX-OS Software Privilege Escalation Vulnerability — Nexus 7000 and 7700 Series Switches 7.8 -2019-03-08
CVE-2018-9867 SonicWall SonicOS 访问控制错误漏洞 — SonicOS 5.5 -2019-02-19
CVE-2019-3820 gnome-shell 授权问题漏洞 — gnome-shell 4.3 -2019-02-06
CVE-2018-14666 Foreman 安全漏洞 — Satellite 8.1 -2019-01-22
CVE-2018-14662 Red Hat Ceph 信息泄露漏洞 — ceph 5.7 -2019-01-15
CVE-2018-15465 Cisco Adaptive Security Appliance Software Privilege Escalation Vulnerability — Cisco Adaptive Security Appliance (ASA) Software 8.1 -2018-12-24
CVE-2018-17933 Vecna VGo Robot 安全漏洞 — VGo Robot 8.8 -2018-10-30
CVE-2018-0459 Cisco Enterprise NFV Infrastructure Software Denial of Service Vulnerability — Cisco Enterprise NFV Infrastructure Software 6.5 -2018-10-05
CVE-2018-0460 Cisco Enterprise NFV Infrastructure Software Information Disclosure Vulnerability — Cisco Enterprise NFV Infrastructure Software 6.5 -2018-10-05
CVE-2018-15405 Cisco Integrated Management Controller Supervisor and Cisco UCS Director Authenticated Web Interface Information Disclosure Vulnerability — Cisco Unified Computing System Director 6.5 -2018-10-05
CVE-2018-3829 Elastic Cloud Enterprise 安全漏洞 — Elastic Cloud Enterprise 6.5 -2018-09-19
CVE-2016-7035 Pacemaker 权限许可和访问控制漏洞 — pacemaker 7.8 -2018-09-10
CVE-2016-7071 Red Hat CloudForms 安全漏洞 — CFME 7.5 -2018-09-10
CVE-2016-7077 Foreman 信息泄露漏洞 — foreman 4.3 -2018-09-10
CVE-2016-7078 Foreman 信息泄露漏洞 — foreman 4.3 -2018-09-10
CVE-2018-3778 aedes 安全漏洞 — aedes 5.3 -2018-08-08
CVE-2018-0391 Cisco Prime Collaboration Provisioning 安全漏洞 — Cisco Prime Collaboration Provisioning unknown 6.5 -2018-08-01
CVE-2018-12466 openbuildservice allowed deleting packages via project links — openbuildservice 6.5 -2018-08-01
CVE-2018-12467 delete package via link exploit in open buildservice — openbuildservice 7.5 -2018-08-01

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