This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "Forced browsing"
| Line 2: | Line 2: | ||
==Description== | ==Description== | ||
| − | |||
Forced browsing is an attack that’s aim to enumerate and access resources that are not referenced by the application, but still can be accessible. | Forced browsing is an attack that’s aim to enumerate and access resources that are not referenced by the application, but still can be accessible. | ||
| Line 11: | Line 10: | ||
This attack is also known as Predictable Resource Location, File Enumeration, Directory Enumeration, and Resource Enumeration. | This attack is also known as Predictable Resource Location, File Enumeration, Directory Enumeration, and Resource Enumeration. | ||
| + | ==Severity== | ||
| + | Medium to High | ||
| + | |||
| + | ==Likelihood of exploitation== | ||
| + | Very High | ||
==Examples == | ==Examples == | ||
| − | |||
===Example 1=== | ===Example 1=== | ||
| − | |||
This example presents a technique of Predictable Resource Location attack, which is based on a manual and oriented identification of resources by modifying URL parameters. | This example presents a technique of Predictable Resource Location attack, which is based on a manual and oriented identification of resources by modifying URL parameters. | ||
The user1 wants to check his on-line agenda that is done thru the following URL: | The user1 wants to check his on-line agenda that is done thru the following URL: | ||
| Line 27: | Line 29: | ||
The attack can be considered successful upon accessing other user agenda. A bad implementation of the authorization mechanism also collaborated for this attack success. | The attack can be considered successful upon accessing other user agenda. A bad implementation of the authorization mechanism also collaborated for this attack success. | ||
| − | |||
===Example 2 === | ===Example 2 === | ||
| − | |||
This example presents how to perform an attack of static directory and file enumeration using an automated tool. | This example presents how to perform an attack of static directory and file enumeration using an automated tool. | ||
| Line 42: | Line 42: | ||
When the tool receives and “HTTP 200” message it means that such resource was found and should be manually inspected for valuable information. | When the tool receives and “HTTP 200” message it means that such resource was found and should be manually inspected for valuable information. | ||
| − | |||
==External References== | ==External References== | ||
| − | |||
*Forceful Browsing – Imperva Application Data Security and Compliance - http://www.imperva.com/application_defense_center/glossary/forceful_browsing.html | *Forceful Browsing – Imperva Application Data Security and Compliance - http://www.imperva.com/application_defense_center/glossary/forceful_browsing.html | ||
| − | |||
*Parameter fuzzing and forced browsing – WebAppSec - http://seclists.org/webappsec/2006/q3/0182.html | *Parameter fuzzing and forced browsing – WebAppSec - http://seclists.org/webappsec/2006/q3/0182.html | ||
| − | |||
*http://www.webappsec.org/projects/threat/classes/predictable_resource_location.shtml | *http://www.webappsec.org/projects/threat/classes/predictable_resource_location.shtml | ||
| − | |||
*http://cwe.mitre.org/data/definitions/425.html | *http://cwe.mitre.org/data/definitions/425.html | ||
| − | |||
==Related Threats== | ==Related Threats== | ||
| − | |||
[[:Category:Information Disclosure]] | [[:Category:Information Disclosure]] | ||
| − | |||
==Related Attacks== | ==Related Attacks== | ||
| − | |||
*[[Path Traversal]] | *[[Path Traversal]] | ||
| − | |||
*[[Path Manipulation]] | *[[Path Manipulation]] | ||
| − | |||
==Related Vulnerabilities== | ==Related Vulnerabilities== | ||
| − | |||
[[:Category:Access Control Vulnerability]] | [[:Category:Access Control Vulnerability]] | ||
| − | |||
==Related Countermeasures== | ==Related Countermeasures== | ||
| Line 76: | Line 63: | ||
[[:Category: Access Control]] | [[:Category: Access Control]] | ||
| − | |||
| − | |||
| − | |||
[[category:Resource Manipulation]] | [[category:Resource Manipulation]] | ||
| + | [[Category:Attack]] | ||
Revision as of 16:34, 5 November 2007
- This is an Attack. To view all attacks, please see the Attack Category page.
Description
Forced browsing is an attack that’s aim to enumerate and access resources that are not referenced by the application, but still can be accessible.
An attacker can use brute force techniques to search for unlinked contents in domain directory, such as temporary directories and files, old backup and configuration files. These resources may store sensitive information about web applications and operational system, such as source code, credentials, internal network addressing, and so on, thus being considered a valuable resource for intruders.
This attack should be performed manually when the application index directories and pages based on number generation or predictable values, or using automated tools for common files and directories names.
This attack is also known as Predictable Resource Location, File Enumeration, Directory Enumeration, and Resource Enumeration.
Severity
Medium to High
Likelihood of exploitation
Very High
Examples
Example 1
This example presents a technique of Predictable Resource Location attack, which is based on a manual and oriented identification of resources by modifying URL parameters. The user1 wants to check his on-line agenda that is done thru the following URL:
www.site-example.com/users/calendar.php/user1/20070715
In the URL, it is possible to identify the username (“user1”) and the date (mm/dd/yyyy).If the user attempts to make a forced browsing attack, he could guess another user’s agenda by predicting user identification and date, as follow:
www.site-example.com/users/calendar.php/user6/20070716
The attack can be considered successful upon accessing other user agenda. A bad implementation of the authorization mechanism also collaborated for this attack success.
Example 2
This example presents how to perform an attack of static directory and file enumeration using an automated tool.
A scanning tool, like | Nikto, has the ability to search for existent files and directories based on a database of well-know resources, such as:
/system/ /password/ /logs/ /admin/ /test/
When the tool receives and “HTTP 200” message it means that such resource was found and should be manually inspected for valuable information.
External References
- Forceful Browsing – Imperva Application Data Security and Compliance - http://www.imperva.com/application_defense_center/glossary/forceful_browsing.html
- Parameter fuzzing and forced browsing – WebAppSec - http://seclists.org/webappsec/2006/q3/0182.html
- http://www.webappsec.org/projects/threat/classes/predictable_resource_location.shtml
- http://cwe.mitre.org/data/definitions/425.html
Related Threats
Category:Information Disclosure
Related Attacks
Related Vulnerabilities
Category:Access Control Vulnerability
