CAPEC-1 Detail

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.

Execution Flow

1) Explore

[Survey] The attacker surveys the target application, possibly as a valid and authenticated user

Technique

• Spidering web sites for all available links
• Brute force guessing of resource names
• Brute force guessing of user names / credentials
• Brute force guessing of function names / actions

2) Explore

[Identify Functionality] At each step, the attacker notes the resource or functionality access mechanism invoked upon performing specific actions

Technique

• Use the web inventory of all forms and inputs and apply attack data to those inputs.
• Use a packet sniffer to capture and record network traffic
• Execute the software in a debugger and record API calls into the operating system or important libraries. This might occur in an environment other than a production environment, in order to find weaknesses that can be exploited in a production environment.

3) Experiment

[Iterate over access capabilities] Possibly as a valid user, the attacker then tries to access each of the noted access mechanisms directly in order to perform functions not constrained by the ACLs.

Technique

• Fuzzing of API parameters (URL parameters, OS API parameters, protocol parameters)

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.

Skills Required

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.

Resources Required

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

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.

Related Weaknesses

Submission

Modifications