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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-863 (授权机制不正确) — Vulnerability Class 1278

1278 vulnerabilities classified as CWE-863 (授权机制不正确). AI Chinese analysis included.

CWE-863, Incorrect Authorization, represents a critical logic flaw where software fails to properly verify an actor’s permissions before granting access to resources or executing actions. Attackers typically exploit this vulnerability by manipulating input parameters, such as altering user IDs or session tokens, to bypass intended access controls and interact with data or functions reserved for privileged users. This often leads to unauthorized data disclosure, modification, or complete system compromise. To prevent such breaches, developers must implement robust, centralized authorization checks that are consistently applied across all application layers. Relying solely on client-side restrictions is insufficient; instead, server-side validation should enforce strict role-based or attribute-based access controls for every request, ensuring that permission verification occurs reliably before any sensitive operation is permitted.

MITRE CWE Description
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Common Consequences (5)
ConfidentialityRead Application Data, Read Files or Directories
An attacker could bypass intended access restrictions to read sensitive data, either by reading the data directly from a data store that is not correctly restricted, or by accessing insufficiently-protected, privileged functionality to read the data.
IntegrityModify Application Data, Modify Files or Directories
An attacker could bypass intended access restrictions to modify sensitive data, either by writing the data directly to a data store that is not correctly restricted, or by accessing insufficiently-protected, privileged functionality to write the data.
Access ControlGain Privileges or Assume Identity, Bypass Protection Mechanism
An attacker could bypass intended access restrictions to gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
Confidentiality, Integrity, AvailabilityExecute Unauthorized Code or Commands
An attacker could use elevated privileges to execute unauthorized commands or code.
AvailabilityDoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Resource Consumption (Other)
An attacker could gain unauthorized access to resources on the system and excessively consume those resources, leading to a denial of service.
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) [REF-229] 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 …
Architecture and DesignEnsure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied 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…
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 (1)
The following code could be for a medical records application. It displays a record to already authenticated users, confirming the user's authorization using a value stored in a cookie.
$role = $_COOKIES['role']; if (!$role) { $role = getRole('user'); if ($role) { // save the cookie to send out in future responses setcookie("role", $role, time()+60*60*2); } else{ ShowLoginScreen(); die("\n"); } } if ($role == 'Reader') { DisplayMedicalHistory($_POST['patient_ID']); } else{ die("You are not Authorized to view this record\n"); }
Bad · PHP
CVE IDTitleCVSSSeverityPublished
CVE-2022-2597 Visual Portfolio < 2.19.0 - Contributor+ CSS Injection — Visual Portfolio, Photo Gallery & Post Grid 5.4 -2022-09-05
CVE-2022-23452 barbican 授权问题漏洞 — openstack/barbican 4.9 -2022-09-01
CVE-2021-3563 Red Hat OpenStack Platform 安全漏洞 — keystone 7.4 -2022-08-26
CVE-2021-3763 AMQ 访问控制错误漏洞 — AMQ Broker 4.3 -2022-08-23
CVE-2022-35692 Adobe Commerce Improper Access Control Security feature bypass — Magento Commerce 5.3 Medium2022-08-19
CVE-2022-36009 Incorrect parsing of access level in gomatrixserverlib and dendrite — gomatrixserverlib 5.0 Medium2022-08-19
CVE-2022-1401 Insufficient validation of provided paths in Exago WrImageResource.axd — CMDB 6.9 Medium2022-08-16
CVE-2020-14321 Moodle 权限许可和访问控制问题漏洞 — Moodle 8.8 -2022-08-16
CVE-2022-33718 SAMSUNG Mobile devices 安全漏洞 — Samsung Mobile Devices 6.2 Medium2022-08-05
CVE-2022-27551 HCL Launch could allow an authenticated user to obtain sensitive information (CVE-2022-27551) — HCL Launch 5.3 Medium2022-08-03
CVE-2022-31178 Improper Authorization in eLabFTW — elabftw 4.3 Medium2022-08-01
CVE-2022-31155 Unauthorized overwriting of saved searches in Sourcegraph — sourcegraph 4.3 Medium2022-08-01
CVE-2022-31154 Indirect Object Access in Sourcegraph Code Monitoring — sourcegraph 6.4 Medium2022-08-01
CVE-2022-0670 Red Hat Ceph 安全漏洞 — Ceph 8.1 -2022-07-25
CVE-2022-0594 Shareaholic < 9.7.6 - Information Disclosure — Professional Social Sharing Buttons, Icons & Related Posts – Shareaholic 5.3 -2022-07-25
CVE-2022-31107 Grafana account takeover via OAuth vulnerability — grafana 7.1 High2022-07-15
CVE-2022-29619 SAP BusinessObjects Business Intelligence Platform 安全漏洞 — SAP BusinessObjects Business Intelligence Platform 8.1 -2022-07-12
CVE-2022-32532 Authentication Bypass Vulnerability — Apache Shiro 9.8 -2022-06-28
CVE-2022-31589 多款SAP产品安全漏洞 — SAP ERP, localization for CEE countries. 6.5 -2022-06-14
CVE-2022-27668 SAP NetWeaver 和 ABAP Platform 安全漏洞 — SAP NetWeaver and ABAP Platform 9.8 -2022-06-14
CVE-2022-30311 FESTO: CECC-X-M1 and Servo Press Kit YJKP OS Command Injection vulnerability — Controller CECC-X-M1 (4407603) 9.8 Critical2022-06-13
CVE-2022-30310 FESTO: CECC-X-M1 and Servo Press Kit YJKP OS Command Injection vulnerability — Controller CECC-X-M1 (4407603) 9.8 Critical2022-06-13
CVE-2022-30309 FESTO: CECC-X-M1 and Servo Press Kit YJKP OS Command Injection vulnerability — Controller CECC-X-M1 (4407603) 9.8 Critical2022-06-13
CVE-2022-30308 FESTO: CECC-X-M1 and Servo Press Kit YJKP OS Command Injection vulnerability — Controller CECC-X-M1 (4407603) 9.8 Critical2022-06-13
CVE-2022-22978 VMware Spring Security 授权问题漏洞 — Spring Security 9.8 -2022-05-19
CVE-2021-3956 Lenovo XClarity Controller 安全漏洞 — XClarity Controller (XCC) 4.3 Medium2022-05-18
CVE-2022-1706 Ignition 访问控制错误漏洞 — coreos/ignition 6.5 -2022-05-17
CVE-2022-28774 SAP Host Agent 信息泄露漏洞 — SAP Host Agent 5.5 -2022-05-11
CVE-2022-0866 Wildfly 安全漏洞 — Wildfly 8.2 -2022-05-10
CVE-2021-36778 Exposure of repository credentials to external third-party sources — Rancher 7.3 High2022-05-02

Vulnerabilities classified as CWE-863 (授权机制不正确) represent 1278 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.