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

Goal: 1000 CNY · Raised: 1336 CNY

100%

CWE-862 (授权机制缺失) — Vulnerability Class 7360

7360 vulnerabilities classified as CWE-862 (授权机制缺失). AI Chinese analysis included.

CWE-862 represents a critical access control weakness where software fails to verify an actor’s permissions before granting access to resources or executing actions. Attackers typically exploit this flaw by manipulating requests to access sensitive data or perform privileged operations that should be restricted to authorized users. Without proper checks, malicious actors can bypass authentication mechanisms entirely, leading to unauthorized data exposure, modification, or system compromise. Developers mitigate this risk by implementing robust authorization logic at every entry point, ensuring that identity verification is coupled with strict permission validation. This involves checking user roles and access rights against the requested resource before processing any request. By integrating these checks into the application’s core architecture and utilizing established frameworks, teams can prevent unauthorized access and maintain the integrity of their systems against exploitation.

MITRE CWE Description
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Common Consequences (4)
Confidentiality Read 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 restricted, or by accessing insufficiently-protected, privileged functionality to read the data.
Integrity Modify 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 restricted, or by accessing insufficiently-protected, privileged functionality to write the data.
Access Control Gain Privileges or Assume Identity, Bypass Protection Mechanism
An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
Availability DoS: 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 Design Divide 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 Design Ensure 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 Design Use 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 Design For 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, Installation Use 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 ID Title CVSS Severity Published
CVE-2021-44794 Information Leakege via Unauthorized Access in Single Connect — Single Connect 5.3 Medium 2022-01-27
CVE-2021-44793 Information Leakege via Unauthorized Access in Single Connect — Single Connect 8.6 High 2022-01-27
CVE-2021-44792 Information Leakege via Unauthorized Access in Single Connect — Single Connect 5.3 Medium 2022-01-27
CVE-2022-23945 Apache ShenYu missing authentication allows gateway registration — Apache ShenYu (incubating) 9.1 - 2022-01-25
CVE-2022-23944 Apache ShenYu 2.4.1 Improper access control — Apache ShenYu (incubating) 9.1 - 2022-01-25
CVE-2021-25013 Qubely < 1.7.8 - Subscriber+ Arbitrary Post Deletion — Qubely – Advanced Gutenberg Blocks 6.5 - 2022-01-24
CVE-2021-24968 Ultimate FAQ < 2.1.2 - Subscriber+ Arbitrary FAQ Creation — Ultimate FAQ – WordPress FAQ and Accordion Plugin 3.5 - 2022-01-24
CVE-2021-24906 Protect WP Admin < 3.6.2 - Unauthenticated Plugin Deactivation — Protect WP Admin 7.5 - 2022-01-24
CVE-2022-0236 WP Import Export (Lite) <= 3.9.15 Unauthenticated Sensitive Data Disclosure — WP Import Export 7.5 High 2022-01-18
CVE-2022-0178 Missing Authorization in snipe/snipe-it — snipe/snipe-it 6.3 Medium 2022-01-13
CVE-2022-0179 Missing Authorization in snipe/snipe-it — snipe/snipe-it 5.4 - 2022-01-12
CVE-2022-22111 DayByDay CRM - Missing Authorization when Changing Password — DaybydayCRM 8.8 High 2022-01-05
CVE-2022-22108 DayByDay CRM - Missing Authorization when Viewing Absences — DaybydayCRM 4.3 Medium 2022-01-05
CVE-2022-22107 DayByDay CRM - Missing Authorization when Viewing Appointments — DaybydayCRM 4.3 Medium 2022-01-05
CVE-2021-24831 Tab - Accordion, FAQ < 1.3.2 - Unauthenticated AJAX Calls — Tab – Accordion, FAQ 7.5 - 2022-01-03
CVE-2021-24997 WP Guppy < 1.3 - Sensitive Information Disclosure — WP Guppy 6.5 - 2021-12-27
CVE-2021-40853 TCMAN GIM missing authorization vulnerability — GIM 7.2 High 2021-12-17
CVE-2021-27859 Missing authorization vulnerability in FatPipe software — WARP 8.8 High 2021-12-15
CVE-2021-27857 FatPipe software allows unauthenticated configuration download — WARP 7.5 High 2021-12-15
CVE-2021-27858 Missing authorization vulnerability in FatPipe software — WARP 5.3 Medium 2021-12-15
CVE-2021-27855 FatPipe software allows privilege escalation — WARP 8.8 High 2021-12-15
CVE-2021-44233 SAP GRC Access Control 安全漏洞 — SAP GRC Access Control 8.8 - 2021-12-14
CVE-2021-24836 Temporary Login Without Password < 1.7.1 - Subscriber+ Plugin's Settings Update — Temporary Login Without Password 4.3 - 2021-12-13
CVE-2021-24790 Contact Form Advanced Database <= 1.0.8 - Unauthorised AJAX Calls — Contact Form Advanced Database 4.3 - 2021-12-13
CVE-2021-43781 Permissions not properly checked in Invenio-Drafts-Resources — invenio-drafts-resources 6.4 Medium 2021-12-06
CVE-2021-24914 Tawk.to Live Chat < 0.6.0 - Subscriber+ Visitor Monitoring & Chat Removal — Tawk.To Live Chat 7.3 - 2021-12-06
CVE-2021-24842 Bulk Datetime Change < 1.12 - Missing Authorisation — Bulk Datetime Change 5.4 - 2021-11-29
CVE-2021-39236 Owners of the S3 tokens are not validated — Apache Ozone 8.1 - 2021-11-19
CVE-2021-39232 Missing admin check for SCM related admin commands — Apache Ozone 8.8 - 2021-11-19
CVE-2021-39231 Missing authentication/authorization on internal RPC endpoints — Apache Ozone 9.1 - 2021-11-19

Vulnerabilities classified as CWE-862 (授权机制缺失) represent 7360 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.