CAPEC Definitions / CAPEC-1
CAPEC-1: Accessing Functionality Not Properly Constrained by ACLs
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.
Extended Description
No Extended Description.
Mitigations
In a J2EE setting, administrators can associate a role that is impossible for the authenticator to grant users, such as NoAccess, with all Servlets to which access is guarded by a limited number of servlets visible to, and accessible by, the user. Having done so, any direct access to those protected Servlets will be prohibited by the web container. In a more general setting, the administrator must mark every resource besides the ones supposed to be exposed to the user as accessible by a role impossible for the user to assume. The default security setting must be to deny access and then grant access only to those resources intended by business logic.
Relationships with other CAPECs
Prerequisites
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.
Related Weaknesses
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
