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-2024-27288 1Panel open source panel project has an unauthorized vulnerability. — 1Panel 6.3 Medium2024-03-06
CVE-2024-24761 Galette public pages accessibility restriction — galette 7.5 High2024-03-06
CVE-2024-28174 JetBrains TeamCity 安全漏洞 — TeamCity 5.8 Medium2024-03-06
CVE-2024-27138 Apache Archiva: disabling user registration is not effective — Apache Archiva 7.5 -2024-03-01
CVE-2024-27139 Apache Archiva: incorrect authentication potentially leading to account takeover — Apache Archiva 9.1 -2024-03-01
CVE-2023-47716 IBM FileNet Content Manager privilege escalation — Filenet Content Manager 6.3 Medium2024-03-01
CVE-2024-26016 Apache Superset: Improper authorization validation on dashboards and charts import — Apache Superset 4.3 Medium2024-02-28
CVE-2024-24779 Apache Superset: Improper data authorization when creating a new dataset — Apache Superset 5.0 Medium2024-02-28
CVE-2024-24773 Apache Superset: Improper validation of SQL statements allows for unauthorized access to data — Apache Superset 4.9 Medium2024-02-28
CVE-2023-3509 Incorrect Authorization in GitLab — GitLab 3.7 Low2024-02-21
CVE-2024-26145 Uninvited user is able to join and mark the attendance of the the private event — discourse-calendar 6.5 Medium2024-02-21
CVE-2023-46241 Potential account take over due to unverified emails from Microsoft Identity Platform — discourse-microsoft-auth 9.1 Critical2024-02-21
CVE-2024-25604 Liferay Portal和Liferay DXP 安全漏洞 — Portal 6.5 Medium2024-02-20
CVE-2024-25149 Liferay Portal和Liferay DXP 安全漏洞 — Portal 5.4 Medium2024-02-20
CVE-2024-1482 Improper Authorization in GitHub Enterprise Server allowed unauthorized workflow execution — Enterprise Server 7.1 High2024-02-14
CVE-2024-24966 F5OS vulnerability — F5OS - Appliance 6.2 Medium2024-02-14
CVE-2023-6152 Grafana 安全漏洞 — Grafana 5.4 Medium2024-02-13
CVE-2024-24774 Missing authorization allows users to access arbitrary security levels on Jira through webhooks (Jira Plugin) — Mattermost 3.4 Low2024-02-09
CVE-2023-43609 Emerson Rosemount GC370XA, GC700XA, GC1500XA Improper Authorization — Rosemount GC370XA 6.9 Medium2024-02-09
CVE-2023-51761 Emerson Rosemount GC370XA, GC700XA, GC1500XA Improper Authentication — Rosemount GC370XA 8.3 High2024-02-09
CVE-2023-6564 Incorrect Authorization in GitLab — GitLab 6.5 Medium2024-02-08
CVE-2024-22208 phpMyFAQ sharing FAQ functionality can easily be abused for phishing purposes — phpMyFAQ 6.5 Medium2024-02-05
CVE-2023-32967 QTS, QuTScloud — QuTScloud 5.0 Medium2024-02-02
CVE-2023-47142 IBM Tivoli Application Dependency Discovery Manager privilege escalation — Tivoli Application Dependency Discovery Manager 7.5 High2024-02-02
CVE-2024-24573 facileManager Privilege Escalation via Mass Assignment — facileManager 8.8 High2024-01-31
CVE-2024-23653 BuildKit interactive containers API does not validate entitlements check — buildkit 9.8 Critical2024-01-31
CVE-2023-49783 No permission checks for editing/deleting records with CSV import form — silverstripe-admin 4.3 Medium2024-01-23
CVE-2023-44401 Silverstripe GraqhQL's view permissions are bypassed for paginated lists of ORM data — silverstripe-graphql 5.3 Medium2024-01-23
CVE-2024-23329 changedetection.io API endpoint is not secured with API token — changedetection.io 3.7 Low2024-01-19
CVE-2023-4812 Incorrect Authorization in GitLab — GitLab 7.6 High2024-01-12

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