CWE-862 Classe Incomplet High likelihood

Missing Authorization

This vulnerability occurs when an application fails to verify whether a user has permission to access specific data or execute certain actions before allowing the request to proceed.

Définition

What is CWE-862?

This vulnerability occurs when an application fails to verify whether a user has permission to access specific data or execute certain actions before allowing the request to proceed.
Missing authorization is a common security flaw where an application assumes a user's identity (authentication) is enough to grant access, skipping the crucial step of checking their specific privileges. Think of it like having a key to enter a building (authentication) but then being able to walk into any office or safe without further checks. This allows attackers, including other authenticated users, to access data or perform functions they shouldn't, such as viewing another user's private information, modifying account settings, or deleting critical resources. To prevent this, developers must implement a consistent and robust authorization layer that validates permissions for every request involving sensitive resources or actions. This involves defining clear roles and permissions, checking them against the requested operation and the target data (e.g., ensuring User A can only edit their own profile, not User B's), and centralizing these checks to avoid inconsistencies. Relying solely on UI element hiding is insufficient, as direct API calls or modified requests can easily bypass such superficial controls.
Vulnerability Diagram CWE-862
Missing Authorization user A logged in GET /orders/42 handler isAuthenticated ✓ // no owner check return Order.find(42) order #42 belongs to B A reads B's data IDOR / BOLA Authentication is enforced; per-resource ownership check is missing.
Impact réel

Real-world CVEs caused by CWE-862

  • CVE-2024-6845

    chatbot Wordpress plugin does not perform authorization on a REST endpoint, allowing retrieval of an API key

  • CVE-2025-2224

    AI-enabled WordPress plugin has a missing capability check for a particular function, allowing changing public status of posts

  • CVE-2022-24730

    Go-based continuous deployment product does not check that a user has certain privileges to update or create an app, allowing adversaries to read sensitive repository information

  • CVE-2009-3168

    Web application does not restrict access to admin scripts, allowing authenticated users to reset administrative passwords.

  • CVE-2009-3597

    Web application stores database file under the web root with insufficient access control (CWE-219), allowing direct request.

  • CVE-2009-2282

    Terminal server does not check authorization for guest access.

  • CVE-2008-5027

    System monitoring software allows users to bypass authorization by creating custom forms.

  • CVE-2009-3781

    Content management system does not check access permissions for private files, allowing others to view those files.

Comment les attaquants l'exploitent

Parcours de l'attaquant étape par étape

  1. 1

    This function runs an arbitrary SQL query on a given database, returning the result of the query.

  2. 2

    While this code is careful to avoid SQL Injection, the function does not confirm the user sending the query is authorized to do so. An attacker may be able to obtain sensitive employee information from the database.

  3. 3

    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 assume that the program stores all private messages for all users in the same directory.

  4. 4

    While the program properly exits if authentication fails, it does not ensure that the message is addressed to the user. As a result, an authenticated attacker could provide any arbitrary identifier and read private messages that were intended for other users.

  5. 5

    One way to avoid this problem would be to ensure that the "to" field in the message object matches the username of the authenticated user.

Exemple de code vulnérable

Vulnerable PHP

This function runs an arbitrary SQL query on a given database, returning the result of the query.

Vulnérable PHP 
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']);
Exemple de code sécurisé

Secure pseudo

Sécurisé pseudo 
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Liste de contrôle de prévention

How to prevent CWE-862

  • 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 same role.
  • 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 to the patient and the patient's doctor [REF-7].
  • 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 that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
  • 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.
Signaux de détection

How to detect CWE-862

Automated Static Analysis Limited

Automated static analysis is useful for detecting commonly-used idioms for authorization. A tool may be able to analyze related configuration files, such as .htaccess in Apache web servers, or detect the usage of commonly-used authorization libraries. Generally, automated static analysis tools have difficulty detecting custom authorization schemes. In addition, the software's design may include some functionality that is accessible to any user and does not require an authorization check; an automated technique that detects the absence of authorization may report false positives.

Automated Dynamic Analysis

Automated dynamic analysis may find many or all possible interfaces that do not require authorization, but manual analysis is required to determine if the lack of authorization violates business logic.

Manual Analysis Moderate

This weakness can be detected using tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session. Specifically, manual static analysis is useful for evaluating the correctness of custom authorization mechanisms.

Manual Static Analysis - Binary or Bytecode SOAR Partial

According to SOAR [REF-1479], the following detection techniques may be useful: ``` Cost effective for partial coverage: ``` Binary / Bytecode disassembler - then use manual analysis for vulnerabilities & anomalies

Dynamic Analysis with Automated Results Interpretation SOAR Partial

According to SOAR [REF-1479], the following detection techniques may be useful: ``` Cost effective for partial coverage: ``` Web Application Scanner Web Services Scanner Database Scanners

Dynamic Analysis with Manual Results Interpretation SOAR Partial

According to SOAR [REF-1479], the following detection techniques may be useful: ``` Cost effective for partial coverage: ``` Host Application Interface Scanner Fuzz Tester Framework-based Fuzzer

Correction automatique Plexicus

Plexicus détecte automatiquement CWE-862 et ouvre une PR de correction en moins de 60 secondes.

Codex Remedium analyse chaque commit, identifie cette faiblesse précise et livre une pull request prête à être relue avec le correctif. Pas de tickets. Pas de transferts.

Obtenir une démo Essayer Plexicus gratuitement
Questions fréquentes

Frequently asked questions

Qu'est-ce que CWE-862 ?

This vulnerability occurs when an application fails to verify whether a user has permission to access specific data or execute certain actions before allowing the request to proceed.

Quelle est la gravité de CWE-862 ?

MITRE évalue la probabilité d'exploitation comme Élevée — cette faiblesse est activement exploitée et doit être priorisée pour la remédiation.

Quels langages ou plateformes sont affectés par CWE-862 ?

MITRE lists the following affected platforms: AI/ML, Web Server, Database Server.

Comment puis-je prévenir CWE-862 ?

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 same role. Ensure that access control checks are performed related to the business logic. These…

Comment Plexicus détecte et corrige CWE-862 ?

Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-862 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.

Où puis-je en savoir plus sur CWE-862 ?

MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/862.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.

Faiblesses associées

Weaknesses related to CWE-862

CWE-285 Parent

Improper Authorization

This vulnerability occurs when an application fails to properly verify whether a user has permission to access specific data or perform…

CWE-1230 Frère

Exposure of Sensitive Information Through Metadata

This vulnerability occurs when an application protects the primary source of sensitive data but fails to secure the metadata derived from…

CWE-1256 Frère

Improper Restriction of Software Interfaces to Hardware Features

This vulnerability occurs when a system's software interfaces to hardware features—like power, clock, or performance management—are not…

CWE-1297 Frère

Unprotected Confidential Information on Device is Accessible by OSAT Vendors

This vulnerability occurs when a semiconductor chip does not properly secure sensitive data, making it accessible to third-party…

CWE-1328 Frère

Security Version Number Mutable to Older Versions

This vulnerability occurs when a hardware system's security version number can be changed, allowing an attacker to downgrade or roll back…

CWE-552 Frère

Files or Directories Accessible to External Parties

This vulnerability occurs when an application exposes files or directories to users who shouldn't have access to them.

CWE-732 Frère

Incorrect Permission Assignment for Critical Resource

This vulnerability occurs when a system grants overly permissive access to a sensitive resource, allowing unauthorized users or processes…

CWE-863 Frère

Incorrect Authorization

This vulnerability occurs when an application checks if a user is allowed to perform an action or access data, but the check is flawed or…

CWE-926 Frère

Improper Export of Android Application Components

This vulnerability occurs when an Android app makes a component (like an Activity, Service, or Content Provider) available to other apps…

Ressources

Further reading

Prêt quand vous l'êtes

Arrêtez de payer par développeur.
Commencez à fermer la boucle.

Plexicus est l'ASPM natif IA qui scanne, filtre, corrige, penteste et explique — de façon autonome. Développeurs illimités, dépôts illimités, actions IA à usage équitable. Vrai niveau gratuit, €269/mo annuel quand vous êtes prêt.

Commencer gratuitement Réserver une démo