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.

Attack Execution Flow

3

1

Step 1

Explore

[Survey] The attacker surveys the target application, possibly as a valid and authenticated user
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

Attack Techniques

Spidering web sites for all available links
Brute force guessing of resource names
IT: Indicizzazione di siti web per tutti i link disponibili
Brute force guessing of user names / credentials
IT: Indicizzazione di siti web per tutti i link disponibili
Brute force guessing of function names / actions
IT: Indicizzazione di siti web per tutti i link disponibili

2

Step 2

Explore

[Identify Functionality] At each step, the attacker notes the resource or functionality access mechanism invoked upon performing specific actions
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.

Attack Techniques

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
IT: Utilizza l'inventario web di tutti i form e input e applica i dati di attacco a quegli input.
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.
IT: Utilizza l'inventario web di tutti i form e input e applica i dati di attacco a quegli input.

3

Step 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.
Fuzzing of API parameters (URL parameters, OS API parameters, protocol parameters)

Attack Techniques

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

CAPEC 1 Accessing Functionality Not Properly Constrained by ACLs

Description

Attack Execution Flow

Step 1

Attack Techniques

Step 2

Attack Techniques

Step 3

Attack Techniques

Mitigations

Consequences

Security Scopes Affected

Potential Impacts

Relationships

Parent CAPECs

Child CAPECs

Related ATT&CK Techniques

Services File Permissions Weakness

Resources Required

CAPEC 1 Accessing Functionality Not Properly Constrained by ACLs

Description

Attack Execution Flow

Step 1

Attack Techniques

Step 2

Attack Techniques

Step 3

Attack Techniques

Mitigations

Consequences

Security Scopes Affected

Potential Impacts

Relationships

Parent CAPECs

Child CAPECs

Related ATT&CK Techniques

Services File Permissions Weakness

Resources Required

Iscriviti alla newsletter