Testing for Directory Traversal
Nowadays, many web applications use and manage files. Using input validation methods not well designed, an aggressor could exploit the system in order to read/write files that are not intended to be accessible; in particular situations it could be possible to execute arbitrary code or system commands.
Description of the Issue
Usually, web servers and web applications implement authentication mechanisms in order to control the access to files and resources. Web servers try to confine users' files inside a "root directory" or "web document root" which represents a physical directory on the file system; users have just to consider this directory as the base directory into the hierarchical structure of the web application. The definition of the privileges is made using Access Control Lists (ACL) that identify which users and groups are supposed to be able to access, modify or execute a specific file on the server. These mechanisms are designed to prevent the access to sensible files from malicious users (example: the common /etc/passwd into Unix-like platform) or to avoid the execution of system commands.
Many web applications use server-side scripts to include different kinds of files: is quite common to use this method to manage graphics templates, load static texts, and so on. Unfortunately, these applications show security issues if the input parameters used (form parameters, cookies values, ...) are not well validated.
In web servers and web applications too, this kind of problem arises in directory traversal/file include attacks; exploiting this kind of vulnerability an attacker is able read directory and files which normally he/she couldn't read, access data outside the web document root, include scripts and other kinds of files from external websites.
For the purpose of the OWASP Testing Guide, we will just consider the security threats related to web applications and not to web server (as the infamous "%5c escape code" into Microsoft IIS web server). We will provide further reading, in the references section, for the interested readers.
This kind of attack is also know as the dot-dot-slash attack (../), path traversal, directory climbing, backtracking.
During an assessment, in order to discover directory traversal and file include flaws, we need to perform two different stages:
- (a) Input Vectors Enumeration (a systematical evaluation of each input vector)
- (b) Exploiting Techniques (a methodical evaluation of each attack technique used by an aggressor to exploit the vulnerability)
Black Box testing and example
(a) Input Vectors Enumeration
As others unvalidated input vulnerabilities, in which an aggressor exploit the insufficient validation/sanitization process, also for the directory traversal is necessary to consider each parameter whose value is provided by the users: form parameters (GET/POST), values inside cookies, values stored into databases from previous client-server interactions, others HTTP header parameters.
Examples of checks to be performed at this stage include:
- Do you notice some parameters which you could recognize as file related into HTTP requests?
- Strange file extension?
- Curious variable name?
http://example.com/getUserProfile.jsp?item=ikki.html http://example.com/index.php?file=content http://example.com/main.cgi?home=index.htm
- Is it possible to identify cookies used by the web application for the dynamic generation of pages/templates?
Cookie: ID=d9ccd3f4f9f18cc1:TM=2166255468:LM=1162655568:S=3cFpqbJgMSSPKVMV:TEMPLATE=flower Cookie: USER=1826cc8f:PSTYLE=GreenDotRed
(b) Exploit Techniques
As next step, during the assessment, we need to analyze the different attack techniques used by an aggressor in order to evaluate the input validation functions present into the web application.
Using the previous examples:
The dynamic page called getUserProfile.jsp is used to load static informations from a file, showing the content to users. An attacker could insert the malicious string "../../../../etc/passwd" to include the password hash file of a Linux/Unix system. Obviously this kind of attack is possible only if the validation checkpoint fails; according to the filesystem privileges, the web application itself must be able to read the file.
To exploit this flaw, an aggressor needs some knowledge on where to blindly find any default files and directories on the system: guessing and trying again until the attack works is usually an easy way to perform a directory climbing.
For the cookies example, we have:
It's also possible to include files (scripts too!) located on external website. Let's see:
The following example will demonstrate how is it possible to show the source code of a CGI component, without using any path traversal chars.
The component called "main.cgi" is located into the same directory of the normal HTML static files used by the application. Sometimes, when the attackers are not so lucky, they need to use special chars (like the "." dot, "%00" null, ...) in order to bypass file extension controls and/or stop the script execution.
It's also very important to notice that when developers implement an input validation function sometimes they don't consider every possible chars encoding. During a Black Box Test is useful to try to inject every kind of chars encoding and also every kind of path definition.
Each operating system use different chars as path separator:
"/" root directory "/" directory separator
"<drive letter>:\" root directory "\" but also "/" directory separator
(Usually on Win, the directory traversal attack is limited to a single partition)
Classic Mac os:
"<drive letter>:" root directory ":" directory separator
We should take in account the following chars encoding:
- URL encoding e double URL encoding
%2e%2e%2f represents ../ %2e%2e/ represents ../ ..%2f represents ../ %2e%2e%5c represents ..\ %2e%2e\ represents ..\ ..%5c represents ..\ %252e%252e%255c represents ..\ ..%255c represents ..\ and so on.
- Unicode/UTF-8 Encoding (It just works in systems which are able to accept overlong UTF-8 sequences)
..%c0%af represents ../ ..%c1%9c represents ..\
Gray Box testing and example
When the analysis is performed with a White Box approach, we have to follow the same methodology as in the Black Box Testing. However, since we can review the source code is possible to search the input vectors (stage (a) of the testing) more easily and accurately. During a source code review we can use simple tools (as the grep command) to search one or more common patterns into the application code: inclusion functions/methods, filesystem operations and so on.
PHP: include(), include_once(), require(), require_once(), fopen(), readfile(), ... JSP/Servlet: java.io.File(), java.io.FileReader(), ... ASP: include file, include virtual, ...
For PHP, we can use:
During a Gray Box Testing is usually possible to discover vulnerabilities that are impossible (or very difficult!) to find performing a Black Box assessment.
Some web applications generate dynamic pages using values and parameters stored into a database; if an attacker could insert crafted directory traversal strings when the application saves the data, probably it will occurs a sort of "indirect" directory traversal attack. This kind of security problems is difficult to find because the parameters inside the inclusion functions seem internal and "safe" but otherwise they are not.
Additionally, reviewing the source code, it is possible to analyze the functions that are supposed to handle invalid input: some developers try to massage invalid input to make it valid, avoiding warnings and errors. This functions are usually prone to security flaws.
Considering a web application with these instructions:
filename = Request.QueryString(“file”); Replace(filename, “/”,”\”); Replace(filename, “..\”,””);
An aggressor could exploit the flaw, as in following example:
file=....//....//boot.ini file=....\\....\\boot.ini file= ..\..\boot.ini
- Security Risks of Unicode
- phpBB Attachment Mod Directory Traversal HTTP POST Injection
- Web Proxy (Burp Suite, Paros, WebScarab, Suru Web Proxy)
- Enconding/Decoding tools
- String searcher (grep, your favorite text editor)
OWASP Testing Guide v2