LIVE NEWSROOM · --:-- · May 24, 2026
A LIBRARY FOR SECURITY RESEARCHERS

CWE WEAKNESSES  /  CWE-284

CWE-284

Improper Access Control

Pillar

What it is

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Access control involves the use of several protection mechanisms such as:- Authentication (proving the identity of an actor)- Authorization (ensuring that a given actor can access a resource), and- Accountability (tracking of activities that were performed)When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc.There are two distinct behaviors that can introduce access control weaknesses:- Specification: incorrect privileges, permissions, ownership, etc. are explicitly specified for either the user or the resource (for example, setting a password file to be world-writable, or giving administrator capabilities to a guest user). This action could be performed by the program or the administrator.- Enforcement: the mecha

Impact

OtherVaries by Context

Mitigations

  • [Architecture and Design, Operation] Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • [Architecture and Design]Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separ

Real-world CVE examples

  • CVE-2023-26463 — Chain: IPSec VPN product uses the same variable for multiple purposes in the same function (CWE-1109), leading to incorrect access control (CWE-284) and expired
  • CVE-2022-24985 — A form hosting website only checks the session authentication status for a single form, making it possible to bypass authentication when there are multiple form
  • CVE-2022-29238 — Access-control setting in web-based document collaboration tool is not properly implemented by the code, which prevents listing hidden directories but does not
  • CVE-2022-23607 — Python-based HTTP library did not scope cookies to a particular domain such that "supercookies" could be sent to any domain on redirect
  • CVE-2021-21972 — Chain: Cloud computing virtualization platform does not require authentication for upload of a tar format file (CWE-306), then uses .. path traversal sequences
  • CVE-2021-37415 — IT management product does not perform authentication for some REST API requests, as exploited in the wild per CISA KEV.
  • CVE-2021-35033 — Firmware for a WiFi router uses a hard-coded password for a BusyBox shell, allowing bypass of authentication through the UART port
  • CVE-2020-10263 — Bluetooth speaker does not require authentication for the debug functionality on the UART port, allowing root shell access
  • CVE-2020-13927 — Default setting in workflow management product allows all API requests without authentication, as exploited in the wild per CISA KEV.
  • CVE-2010-4624 — Bulletin board applies restrictions on number of images during post creation, but does not enforce this on editing.
Test & detect

Browse all common weaknesses, check related exploited CVEs, or map to ATT&CK techniques.

Source: MITRE CWE. View on cwe.mitre.org →

Scroll to Top