cve.bz

CAPEC-127

Directory Indexing

Medium severityHigh likelihoodDetailed pattern

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.

On this page

Ask an AI about this attack pattern

ChatGPTClaudeGoogle AI Mode

Show the promptExplain the attack pattern CAPEC-127: Directory Indexing: how it unfolds, what it needs and how to prevent and detect it in my systems. Use https://capec.mitre.org/data/definitions/127.html and https://cve.bz/cve/capec/127?via=ask-ai-copy, which lists recent CVEs with the weaknesses it exploits. Cite the sources.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this attack pattern's id and public links.

How the attack unfolds

  1. Explore

    The attacker looks for a way in.

    1. [Directory Discovery] Use a method, either manual, scripted, or automated to discover the directories on the server by making requests for directories that may possibly exist. During this phase the adversary is less concerned with whether a directory can be accessed or indexed and more focused on simply discovering what directories do exist on the target.

      3 techniques
      • Send requests to the web server for common directory names
      • If directories are discovered that are native to a server type further refine the directory search to include directories usually present on those types of servers.
      • Search for uncommon or potentially user created directories that may be present.

  2. Experiment

    They probe what they found.

    1. [Iteratively explore directory/file structures] The adversary attempts to access the discovered directories that allow access and may attempt to bypass server or application level ACLs by using manual or automated methods

      5 techniques
      • Use a scanner tool to dynamically add directories/files to include their scan based upon data obtained in initial probes.
      • Use a browser to manually explore the website by issuing a request ending the URL in a slash '/'.
      • Attempt to bypass ACLs on directories by using methods that known to work against some server types by appending data to the directory request. For instance, appending a Null byte to the end of the request which may cause an ACL to fail and allow access.
      • Sequentially request a list of common base files to each directory discovered.
      • Try multiple fuzzing techniques to list directory contents for directories that will not reveal their contents with a "/" request

  3. Exploit

    They carry out the attack.

    1. [Read directories or files which are not intended for public viewing.] The adversary attempts to access the discovered directories that allow access and may attempt to bypass server or application level ACLs by using manual or automated methods

      6 techniques
      • Try multiple exploit techniques to list directory contents for directories that will not reveal their contents with a "/" request
      • Try other known exploits to elevate privileges sufficient to bypass protected directories.
      • List the files in the directory by issuing a request with the URL ending in a "/" slash.
      • Access the files via direct URL and capture contents.
      • Attempt to bypass ACLs on directories by using methods that are known to work against some server types by appending data to the directory request. For instance, appending a Null byte to the end of the request which may cause an ACL to fail and allow access.
      • Sequentially request a list of common base files to each directory discovered.

Prerequisites

  • 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

  • Low skill

    To issue the request to URL without given a specific file name

  • High skill

    To bypass the access control of the directory of listings

Resources required

  • Ability to send HTTP requests to a web application.

Consequences

What a successful attack can lead to
ImpactAffectsNote
Read DataConfidentialityInformation Leakage

Mitigations

  • 1. Using blank index.html: putting blank index.html simply prevent directory listings from displaying to site visitors.

  • 2. Preventing with .htaccess in Apache web server: In .htaccess, write "Options-indexes".

  • 3. Suppressing error messages: using error 403 "Forbidden" message exactly like error 404 "Not Found" message.

Weaknesses it exploits

  • CWE-276 Incorrect Default Permissions
  • CWE-285 Improper Authorization
  • CWE-288 Authentication Bypass Using an Alternate Path or Channel
  • CWE-424 Improper Protection of Alternate Path
  • CWE-425 Direct Request
  • CWE-693 Protection Mechanism Failure
  • CWE-732 Incorrect Permission Assignment for Critical Resource

Recent CVEs with these weaknesses

  1. 6.3CVE-2026-28702

    Incorrect default permissions for the Intel(R) VTune(TM) Profiler software within Ring 3: User Applications may allow an escalation of privilege. Unprivileged software adversary with an unauthenticated user combined with a high complexity …

  2. 5.4CVE-2026-20880

    Incorrect default permissions for some Intel(R) Graphics Driver software installers within Ring 3: User Applications may allow an escalation of privilege. Unprivileged software adversary with an authenticated user combined with a high comp…

  3. 5.4CVE-2026-20756

    Incorrect default permissions for some Intel(R) Graphics Driver software installers within Ring 3: User Applications may allow an escalation of privilege. Unprivileged software adversary with an authenticated user combined with a high comp…

  4. –CVE-2026-111264

    The security constraint generated for EJB JAX-WS endpoints with configured authentication protects only some HTTP methods. A remote unauthenticated attacker can bypass authentication by sending requests with another HTTP method. Users are …

  5. 7.8CVE-2026-121267

    Incorrect default permissions vulnerability in TÜBİTAK BİLGEM Software Technologies Research Institute eta-remote allows Accessing Functionality Not Properly Constrained by ACLs. This issue affects eta-remote: from 0.0.2 before 0.0.3.

  6. 3.9CVE-2026-14543

    The VAPIX Edge storage API, enabling the escalation of user privileges by circumventing filesystem isolation, granting unauthorized access to protected system resources. This flaw can only be exploited after authenticating with an admin-pr…

  7. 7.4CVE-2026-12963

    A vulnerability that could allow a viewer account to gain unauthorized access to network attached storage devices on the server.

  8. 7.3CVE-2026-112125

    Incorrect Permission Assignment for Critical Resource Vulnerability in HA Monitor. This issue affects HA Monitor: from 01-00 before 01-83-01.

The newest records naming one of them. Each weakness's page lists them all.

Part of

Examples

The adversary uses directory listing to view sensitive files in the application. This is an example of access…

The adversary uses directory listing to view sensitive files in the application. This is an example of accessing the backup file. The attack issues a request for http://www.example.com/admin/ and receives the following dynamic directory indexing content in the response: Index of /admin Name Last Modified Size Description backup/ 31-May-2007 08:18 - Apache/ 2.0.55 Server at www.example.com Port 80

The target application does not have direct hyperlink to the "backup" directory in the normal html webpage, however the attacker has learned of this directory due to indexing the content. The client then requests the backup directory URL and receives output which has a "db_dump.php" file in it. This sensitive data should not be disclosed publicly.

MITRE's words, unchanged: CAPEC-127 at MITRE. CAPEC is Copyright © 2007–2026, The MITRE Corporation, used under the CAPEC terms of use: “The MITRE Corporation (MITRE) hereby grants you a non-exclusive, royalty-free license to use Common Attack Pattern Enumeration and Classification (CAPEC™) for research, development, and commercial purposes. Any copy you make for such purposes is authorized provided that you reproduce MITRE’s copyright designation and this license in any such copy.” CAPEC and the CAPEC logo are trademarks of The MITRE Corporation. Credits. All attack patterns.