Home > CAPEC List > CAPEC-1: Accessing Functionality Not Properly Constrained by ACLs (Version 2.9)  

CAPEC-1: Accessing Functionality Not Properly Constrained by ACLs

 
Accessing Functionality Not Properly Constrained by ACLs
Definition in a New Window Definition in a New Window
Attack Pattern ID: 1
Abstraction: Standard
Status: Draft
Completeness: Complete
Presentation Filter:
+ Summary

In applications, particularly web applications, access to functionality is mitigated by the authorization framework, whose job it is to map 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 he is otherwise not supposed to.

+ Attack Execution Flow
Explore
  1. Survey:

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

    Attack Step Techniques

    IDAttack Step Technique DescriptionEnvironments
    1

    Spidering web sites for all available links

    env-Web
    2

    Brute force guessing of resource names

    env-All
    3

    Brute force guessing of user names / credentials

    env-All
    4

    Brute force guessing of function names / actions

    env-All

    Indicators

    IDTypeIndicator DescriptionEnvironments
    1Positive

    ACLs or other access control mechanisms are present in the software

    env-Web env-ClientServer
    2Positive

    User IDs or other credentials are present in the software

    env-Web env-ClientServer
    3Positive

    Operating modes with different privileges are present in the software

    env-ClientServer env-Local env-Embedded
  2. Identify Functionality:

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

    Attack Step Techniques

    IDAttack Step Technique DescriptionEnvironments
    1

    Use the web inventory of all forms and inputs and apply attack data to those inputs.

    env-Web
    2

    Use a packet sniffer to capture and record network traffic

    env-CommProtocol
    3

    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.

    env-Local env-Embedded

    Outcomes

    IDTypeOutcome Description
    1Success
    The attacker produces a list of functionality or data that can be accessed through the system.
Experiment
  1. 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.

    Attack Step Techniques

    IDAttack Step Technique DescriptionEnvironments
    1

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

    env-Web env-Local env-Embedded env-ClientServer

    Indicators

    IDTypeIndicator DescriptionEnvironments
    1Negative

    Attempts to create a catalog of access mechanisms and data have failed.

    env-All

    Outcomes

    IDTypeOutcome Description
    1Success
    Functionality is accessible to unauthorized users.
+ Attack 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.

+ Typical Severity

High

+ Typical Likelihood of Exploit

Likelihood: Very High

+ Methods of Attack
  • Analysis
  • Brute Force
+ Examples-Instances

Description

Implementing the Model-View-Controller (MVC) within Java EE's Servlet paradigm using a "Single front controller" pattern that demands that brokered HTTP requests be authenticated before hand-offs to other Action Servlets.

If no security-constraint is placed on those Action Servlets, such that positively no one can access them, the front controller can be subverted.

+ Attacker Skills or Knowledge Required

Skill or Knowledge Level: Low

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

+ Resources Required

No special resources are required for the exploit of this pattern.

+ Probing Techniques

In the case of web applications, use of a spider or other crawling software can allow an attacker to search for accessible pages not beholden to a security constraint.

More generally, noting the target resource accessed upon performing specific actions drives an understanding of the resources accessible from the current context.

+ Solutions and 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.

+ Attack Motivation-Consequences
ScopeTechnical ImpactNote
Confidentiality
Access_Control
Authorization
Gain privileges / assume identity
+ Relevant Security Requirements

All resources must be constrained to be inaccessible by default followed by selectively allowing access to resources as dictated by application and business logic

In addition to a central controller, every resource must also restrict, wherever possible, incoming accesses as dictated by the relevant ACL.

+ Purposes
  • Penetration
+ CIA Impact
Confidentiality Impact: HighIntegrity Impact: MediumAvailability Impact: Low
+ Technical Context
Architectural Paradigms
All
Frameworks
All
Platforms
All
Languages
All
+ Content History
Submissions
SubmitterOrganizationDateSource
CAPEC Content TeamThe MITRE Corporation2014-06-23Internal_CAPEC_Team

More information is available — Please select a different filter.
Page Last Updated or Reviewed: December 07, 2015