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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

1279 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-47037 Apache Airflow missing fix for CVE-2023-40611 in 2.7.1 (DAG run broken access) — Apache Airflow 5.4 -2023-11-12
CVE-2023-4379 Incorrect Authorization in GitLab — GitLab 8.1 High2023-11-09
CVE-2023-46244 Privilege escalation in Xwiki platform — xwiki-platform 9.1 Critical2023-11-07
CVE-2023-46139 KernelSU signature validation mismatch — KernelSU 5.0 Medium2023-10-30
CVE-2023-38218 Incorrect Authorization - Customer account takeover — Adobe Commerce 8.8 High2023-10-13
CVE-2023-41882 vantage6 Improper Access Control vulnerability — vantage6 5.4 Medium2023-10-11
CVE-2023-28635 Defining resource name as integer in vantage6 may give unintended access — vantage6 5.4 Medium2023-10-11
CVE-2023-5521 Incorrect Authorization in tiann/kernelsu — tiann/kernelsu 8.3 -2023-10-11
CVE-2023-36556 Fortinet FortiMail 安全漏洞 — FortiMail 8.6 High2023-10-10
CVE-2022-3248 Openshift api admission checks does not enforce "custom-host" permissions — kubernetes 4.4 Medium2023-10-05
CVE-2023-4997 Improper authorisation in Uptime DC — UptimeDC 8.8 High2023-10-04
CVE-2023-5106 Incorrect Authorization in GitLab — GitLab 8.2 High2023-10-02
CVE-2023-5194 A system/user manager can demote / deactivate another manager — Mattermost 2.7 Low2023-09-29
CVE-2023-5195 A team member can soft delete other teams that they are not part of — Mattermost 6.5 Medium2023-09-29
CVE-2023-5193 System Role with manage posts permission can read posts of Direct Messages — Mattermost 4.9 Medium2023-09-29
CVE-2023-5159 A User Manager role with user edit permissions could manage/update bots — Mattermost 3.8 Low2023-09-29
CVE-2023-5198 Incorrect Authorization in GitLab — GitLab 4.3 Medium2023-09-29
CVE-2023-3920 Incorrect Authorization in GitLab — GitLab 4.3 Medium2023-09-29
CVE-2023-3979 Incorrect Authorization in GitLab — GitLab 3.1 Low2023-09-29
CVE-2023-4532 Incorrect Authorization in GitLab — GitLab 4.3 Medium2023-09-29
CVE-2023-5009 Incorrect Authorization in GitLab — GitLab 9.6 High2023-09-19
CVE-2023-40611 Apache Airflow Dag Runs Broken Access Control Vulnerability — Apache Airflow 7.1 -2023-09-12
CVE-2023-37881 Weak Access Control between Domains in Wing FTP Server <= 7.2.0 — Wing FTP Server 4.9 Medium2023-09-12
CVE-2023-40309 Missing Authorization check in SAP CommonCryptoLib — SAP CommonCryptoLib 9.8 Critical2023-09-12
CVE-2023-32672 Apache Superset: SQL parser edge case bypasses data access authorization — Apache Superset 4.3 Medium2023-09-06
CVE-2023-27523 Apache Superset: Improper data permission validation on Jinja templated queries — Apache Superset 5.0 Medium2023-09-06
CVE-2023-27526 Apache Superset: Improper Authorization check on import charts — Apache Superset 4.3 Medium2023-09-06
CVE-2023-36387 Apache Superset: Improper API permission for low privilege users — Apache Superset 5.4 Medium2023-09-06
CVE-2023-0120 Incorrect Authorization in GitLab — GitLab 3.5 Low2023-09-01
CVE-2023-40168 Malicious projects can read and upload arbitrary files from disk in TurboWarp Desktop — desktop 7.4 High2023-08-17

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