CAPEC-127: Directory Indexing

Description
An adversary crafts a request to a target that results in the target listing/indexing the content of a directory as output. One common method of triggering directory contents as output is to construct a request containing a path that terminates in a directory name rather than a file name since many applications are configured to provide a list of the directory's contents when such a request is received. An adversary can use this to explore the directory tree on a target as well as learn the names of files. This can often end up revealing test files, backup files, temporary files, hidden files, configuration files, user accounts, script contents, as well as naming conventions, all of which can be used by an attacker to mount additional attacks.
Extended Description

If access control mechanisms are absent or misconfigured, a user may be able to access resources that are intended only for higher level users. An adversary may be able to exploit this to utilize a less trusted account to gain information and perform activities reserved for more trusted accounts.

This attack differs from privilege escalation and other privilege stealing attacks in that the adversary never actually escalates their privileges but instead is able to use a lesser degree of privilege to access resources that should be (but are not) reserved for higher privilege accounts. Likewise, the adversary does not exploit trust or subvert systems - all control functionality is working as configured but the configuration does not adequately protect sensitive resources at an appropriate level.

Severity :

Medium

Possibility :

High

Type :

Detailed
Relationships with other CAPECs

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

Prerequisites

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

  • The target must be misconfigured to return a list of a directory's content when it receives a request that ends in a directory name rather than a file name.
  • The adversary must be able to control the path that is requested of the target.
  • The administrator must have failed to properly configure an ACL or has associated an overly permissive ACL with a particular directory.
  • The server version or patch level must not inherently prevent known directory listing attacks from working.
Skills required

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

  • Low To issue the request to URL without given a specific file name
  • High To bypass the access control of the directory of listings
Taxonomy mappings

Mappings to ATT&CK, OWASP and other frameworks.

Resources required

Ability to send HTTP requests to a web application.

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