CAPEC-127: Directory Indexing
Description
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.
Related CWE
A Related Weakness relationship associates a weakness with this attack pattern. Each association implies a weakness that must exist for a given attack to be successful.
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 ('Forced Browsing')
CWE-693: Protection Mechanism Failure
CWE-732: Incorrect Permission Assignment for Critical Resource
Visit http://capec.mitre.org/ for more details.