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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

5581 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)
ConfidentialityRead 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.
IntegrityModify 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 ControlGain Privileges or Assume Identity, Bypass Protection Mechanism
An attacker could gain privileges by modifying or reading critical data directly, or by accessing privileged functionality.
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 (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 IDTitleCVSSSeverityPublished
CVE-2021-24977 Use Any Font < 6.2.1 - Unauthenticated Arbitrary CSS Appending — Use Any Font | Custom Font Uploader 6.1 -2022-02-28
CVE-2021-24730 Logo Showcase with Slick Slider < 1.2.5 - Subscriber+ Arbitrary Media Title/Description/Alt Text/URL Update — Logo Showcase with Slick Slider – Logo Carousel, Logo Slider & Logo Grid 4.3 -2022-02-28
CVE-2022-0726 Missing Authorization in chocobozzz/peertube — chocobozzz/peertube 5.4 -2022-02-23
CVE-2021-25075 Duplicate Page or Post < 1.5.1 - Arbitrary Settings Update to Stored XSS — Duplicate Page or Post 5.7 -2022-02-21
CVE-2020-25718 Samba 信息泄露漏洞 — samba 8.1 -2022-02-18
CVE-2022-0611 Missing Authorization in snipe/snipe-it — snipe/snipe-it 6.3 Medium2022-02-15
CVE-2022-0588 Missing Authorization in librenms/librenms — librenms/librenms 7.1 High2022-02-15
CVE-2022-0579 Missing Authorization in snipe/snipe-it — snipe/snipe-it 6.5 Medium2022-02-14
CVE-2021-25018 PPOM for WooCommerce < 24.0 - Subscriber+ Settings Update to Stored XSS — PPOM for WooCommerce 5.4 -2022-02-14
CVE-2021-25014 Ibtana < 1.1.4.9 - Subscriber+ Settings Update to Stored XSS — Ibtana – WordPress Website Builder 3.5 -2022-02-14
CVE-2022-22535 SAP ERP HCM 安全漏洞 — SAP ERP HCM (Portugal)--2022-02-09
CVE-2022-24317 Schneider Electric Interactive Graphical SCADA System 安全漏洞 — Interactive Graphical SCADA System Data Server (V15.0.0.22020 and prior) 7.5 -2022-02-09
CVE-2022-23621 Missing authorization in xwiki-platform — xwiki-platform 5.5 Medium2022-02-09
CVE-2022-23617 Missing authorization in xwiki-platform — xwiki-platform 6.5 Medium2022-02-09
CVE-2022-21660 Missing authorization in gin-vue-admin — gin-vue-admin 8.1 High2022-02-09
CVE-2021-25084 Advanced Cron Manager - Subscriber+ Arbitrary Events/Schedules Creation/Deletion — Advanced Cron Manager 4.3 -2022-02-07
CVE-2021-24993 Ultimate Product Catalog < 5.0.26 - Subscriber+ Arbitrary Product Creation & Settings Update — Ultimate Product Catalog – WordPress Catalog Plugin 4.3 -2022-02-07
CVE-2021-24839 SupportCandy < 2.2.5 - Unauthenticated Arbitrary Ticket Deletion — SupportCandy – Helpdesk & Support Ticket System 7.5 -2022-02-07
CVE-2022-0218 WP HTML Mail <= 3.0.9 Missing Authorization on REST-API Route — WP HTML Mail 8.3 High2022-02-04
CVE-2021-25093 Link Library < 7.2.8 - Unauthenticated Arbitrary Links Deletion — Link Library 7.5 -2022-02-01
CVE-2021-44795 Modifying User Permissions via Unauthorized Access in Single Connect — Single Connect 5.3 Medium2022-01-27
CVE-2021-44794 Information Leakege via Unauthorized Access in Single Connect — Single Connect 5.3 Medium2022-01-27
CVE-2021-44793 Information Leakege via Unauthorized Access in Single Connect — Single Connect 8.6 High2022-01-27
CVE-2021-44792 Information Leakege via Unauthorized Access in Single Connect — Single Connect 5.3 Medium2022-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 High2022-01-18

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