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-2023-52943 Synology Surveillance Station 安全漏洞 — Surveillance Station 4.3 Medium2024-12-04
CVE-2024-11669 Incorrect Authorization in GitLab — GitLab 6.5 Medium2024-11-26
CVE-2024-7915 macOS Sensei Mac Cleaner Local Privilege Escalation via PID Reuse - Race Condition Attack — Sensei Mac Cleaner 7.8 High2024-11-25
CVE-2024-11670 Devolutions Remote Desktop Manager 安全漏洞 — Remote Desktop Manager 8.8AIHighAI2024-11-25
CVE-2024-11672 Devolutions Remote Desktop Manager 安全漏洞 — Remote Desktop Manager 6.5AIMediumAI2024-11-25
CVE-2024-11176 Incorrect evaluation of effective permissions in M-Files Aino — M-Files Aino 6.5AIMediumAI2024-11-20
CVE-2024-52584 Autolab has vulnerable submission endpoints — Autolab 5.4AIMediumAI2024-11-18
CVE-2024-3379 Incorrect Authorization in lunary-ai/lunary — lunary-ai/lunary 7.1 -2024-11-14
CVE-2024-9693 Incorrect Authorization in GitLab — GitLab 8.5 High2024-11-14
CVE-2024-50310 Siemens SIMATIC CP 1543-1 安全漏洞 — SIMATIC CP 1543-1 V4.0 7.5 High2024-11-12
CVE-2024-42000 Unauthorized Access to view channels' details — Mattermost 2.7 Low2024-11-09
CVE-2024-52314 data.all admin user may access potentially sensitive data stored by producers via logs — data.all 4.9 Medium2024-11-09
CVE-2024-52312 data.all authenticated users can perform restricted operations against DataSets and Environments — data.all 5.4 Medium2024-11-09
CVE-2024-10953 data.all authenticated users can perform mutating update operations on persisted notification records — data.all 4.3 Medium2024-11-09
CVE-2024-10975 Nomad Vulnerable To Cross-Namespace Volume Creation Abusing CSI Write Permission — Nomad 7.7 High2024-11-07
CVE-2024-20537 Cisco Identity Services Engine Authorization Bypass Vulnerability — Cisco Identity Services Engine Software 6.5 Medium2024-11-06
CVE-2024-9902 Ansible-core: ansible-core user may read/write unauthorized content 6.3 Medium2024-11-06
CVE-2024-49256 WordPress Htaccess File Editor plugin <= 1.0.18 - Broken Access Control vulnerability — Htaccess File Editor 6.5 Medium2024-11-01
CVE-2024-49501 OMRON Sysmac Studio 安全漏洞 — SYSMAC-SE2[][][] 9.8AICriticalAI2024-11-01
CVE-2024-50419 WordPress Greenshift plugin <=9.7 - Broken Access Control vulnerability — Greenshift 5.4 Medium2024-10-30
CVE-2024-9825 The Chef Habitat builder is impacted by Indirect Object reference(IDOR) by deletion of personal access token — Chef Habitat Builder 5.4 Medium2024-10-28
CVE-2024-10295 Gateway: apicast basic auth bypass via malformed base64 headerssending non-base64 'basic' auth with special characters causes apicast to incorrectly authenticate a request 7.5 High2024-10-24
CVE-2024-20482 Cisco Secure Firewall Management Center 安全漏洞 — Cisco Firepower Management Center 6.5 Medium2024-10-23
CVE-2024-48911 OpenCanary Executes Commands From Potentially Writable Config File — opencanary 8.8AIHighAI2024-10-14
CVE-2024-8970 Incorrect Authorization in GitLab — GitLab 8.2 High2024-10-11
CVE-2024-45128 Adobe Commerce | Incorrect Authorization (CWE-863) — Adobe Commerce 5.4 Medium2024-10-10
CVE-2024-45132 Adobe Commerce | Incorrect Authorization (CWE-863) — Adobe Commerce 6.5 Medium2024-10-10
CVE-2024-45131 Adobe Commerce | Incorrect Authorization (CWE-863) — Adobe Commerce 5.4 Medium2024-10-10
CVE-2024-45125 Adobe Commerce | Incorrect Authorization (CWE-863) — Adobe Commerce 4.3 Medium2024-10-10
CVE-2024-9623 Incorrect Authorization in GitLab — GitLab 4.9 Medium2024-10-10

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