CAPEC-1: Accessing Functionality Not Properly Constrained by ACLs

Description
In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.

Severity :

High

Possibility :

High

Type :

Standard
Relationships with other CAPECs

This table shows the other attack patterns and high level categories that are related to this attack pattern.

CAPEC-17: Using Malicious Files Using Malicious Files CAPEC-58: Restful Privilege Elevation Restful Privilege Elevation CAPEC-122: Privilege Abuse Privilege Abuse CAPEC-679: Exploitation of Improperly Configured or Implemented Memory Protections Exploitation of Improperly Configured or Implemented Memory Protections CAPEC-680: Exploitation of Improperly Controlled Registers Exploitation of Improperly Controlled Registers CAPEC-681: Exploitation of Improperly Controlled Hardware Security Identifiers Exploitation of Improperly Controlled Hardware Security Identifiers
Prerequisites

This table shows the other attack patterns and high level categories that are related to this attack pattern.

  • The application must be navigable in a manner that associates elements (subsections) of the application with ACLs.
  • The various resources, or individual URLs, must be somehow discoverable by the attacker
  • The administrator must have forgotten to associate an ACL or has associated an inappropriately permissive ACL with a particular navigable resource.
Skills required

This table shows the other attack patterns and high level categories that are related to this attack pattern.

  • Low In order to discover unrestricted resources, the attacker does not need special tools or skills. They only have to observe the resources or access mechanisms invoked as each action is performed and then try and access those access mechanisms directly.
Taxonomy mappings

Mappings to ATT&CK, OWASP and other frameworks.

ATTACK | Hijack Execution Flow: ServicesFile Permissions Weakness
Resources required

None: No specialized resources are required to execute this type of attack.

Related CWE

A Related Weakness relationship associates a weakness with this attack pattern. Each association implies a weakness that must exist for a given attack to be successful.

CWE-276: Incorrect Default Permissions

CWE-285: Improper Authorization

CWE-434: Unrestricted Upload of File with Dangerous Type

CWE-693: Protection Mechanism Failure

CWE-732: Incorrect Permission Assignment for Critical Resource

CWE-1191: On-Chip Debug and Test Interface With Improper Access Control

CWE-1193: Power-On of Untrusted Execution Core Before Enabling Fabric Access Control

CWE-1220: Insufficient Granularity of Access Control

CWE-1297: Unprotected Confidential Information on Device is Accessible by OSAT Vendors

CWE-1311: Improper Translation of Security Attributes by Fabric Bridge

CWE-1314: Missing Write Protection for Parametric Data Values

CWE-1315: Improper Setting of Bus Controlling Capability in Fabric End-point

CWE-1318: Missing Support for Security Features in On-chip Fabrics or Buses

CWE-1320: Improper Protection for Outbound Error Messages and Alert Signals

CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')

CWE-1327: Binding to an Unrestricted IP Address

Visit http://capec.mitre.org/ for more details.