The Path Traversal attack technique allows an attacker access to files, directories, and commands that potentially reside outside the web document root directory. An attacker may manipulate a URL in such a way that the web site will execute or reveal the contents of arbitrary files anywhere on the web server. Any device that exposes an HTTP-based interface is potentially vulnerable to Path Traversal.
Most web sites restrict user access to a specific portion of the file-system, typically called the "web document root" or "CGI root" directory. These directories contain the files intended for user access and the executable necessary to drive web application functionality. To access files or execute commands anywhere on the file-system, Path Traversal attacks will utilize the ability of special-characters sequences.
The most basic Path Traversal attack uses the "../" special-character sequence to alter the resource location requested in the URL. Although most popular web servers will prevent this technique from escaping the web document root, alternate encodings of the "../" sequence may help bypass the security filters. These method variations include valid and invalid Unicode-encoding ("..%u2216" or "..%c0%af") of the forward slash character, backslash characters ("..\") on Windows-based servers, URL encoded characters "%2e%2e%2f"), and double URL encoding ("..%255c") of the backslash character.
Even if the web server properly restricts Path Traversal attempts in the URL path, a web application itself may still be vulnerable due to improper handling of user-supplied input. This is a common problem of web applications that use template mechanisms or load static text from files. In variations of the attack, the original URL parameter value is substituted with the file name of one of the web application's dynamic scripts. Consequently, the results can reveal source code because the file is interpreted as text instead of an executable script. These techniques often employ additional special characters such as the dot (".") to reveal the listing of the current working directory, or "%00" NULL characters in order to bypass rudimentary file extension checks.
+ + + +* URL: [http://127.0.0.1:8000/taskManager/tutorials/components/?query=c%3A%2F](http://127.0.0.1:8000/taskManager/tutorials/components/?query=c%3A%2F) + + + * Method: `GET` + + + * Parameter: `query` + + + * Attack: `c:/` + + + * Evidence: `etc` + + + + +Instances: 1 + +### Solution +Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a whitelist of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. Do not rely exclusively on looking for malicious or malformed inputs (i.e., do not rely on a blacklist). However, blacklists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if you are expecting colors such as "red" or "blue."
For filenames, use stringent whitelists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses, and exclude directory separators such as "/". Use a whitelist of allowable file extensions.
Warning: if you attempt to cleanse your data, then do so that the end result is not in the form that can be dangerous. A sanitizing mechanism can remove characters such as '.' and ';' which may be required for some exploits. An attacker can try to fool the sanitizing mechanism into "cleaning" data into a dangerous form. Suppose the attacker injects a '.' inside a filename (e.g. "sensi.tiveFile") and the sanitizing mechanism removes the character resulting in the valid filename, "sensitiveFile". If the input data are now assumed to be safe, then the file may be compromised.
Inputs should be decoded and canonicalized to the application's current internal representation before being validated. Make sure that your application does not decode the same input twice. Such errors could be used to bypass whitelist schemes by introducing dangerous inputs after they have been checked.
Use a built-in path canonicalization function (such as realpath() in C) that produces the canonical version of the pathname, which effectively removes ".." sequences and symbolic links.
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by your software.
OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows you to specify restrictions on file operations.
This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise.
+ +### Reference +* http://projects.webappsec.org/Path-Traversal +* http://cwe.mitre.org/data/definitions/22.html + + +#### CWE Id : 22 + +#### WASC Id : 33 + +#### Source ID : 1 + + + + +### Web Browser XSS Protection Not Enabled +##### Low (Medium) + + + + +#### Description +Web Browser XSS Protection is not enabled, or is disabled by the configuration of the 'X-XSS-Protection' HTTP response header on the web server
+ + + +* URL: [http://127.0.0.1:8000](http://127.0.0.1:8000) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/sitemap.xml](http://127.0.0.1:8000/sitemap.xml) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/taskManager/tutorials/components/](http://127.0.0.1:8000/taskManager/tutorials/components/) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/taskManager/tutorials/access/](http://127.0.0.1:8000/taskManager/tutorials/access/) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/taskManager/tutorials/injection/](http://127.0.0.1:8000/taskManager/tutorials/injection/) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/taskManager/tutorials/](http://127.0.0.1:8000/taskManager/tutorials/) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/static/taskManager/js/bootstrap.min.js](http://127.0.0.1:8000/static/taskManager/js/bootstrap.min.js) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/taskManager/](http://127.0.0.1:8000/taskManager/) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/taskManager/register/](http://127.0.0.1:8000/taskManager/register/) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/taskManager/login/](http://127.0.0.1:8000/taskManager/login/) + + + * Method: `POST` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/](http://127.0.0.1:8000/) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/taskManager/tutorials/exposure/](http://127.0.0.1:8000/taskManager/tutorials/exposure/) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/taskManager/register/](http://127.0.0.1:8000/taskManager/register/) + + + * Method: `POST` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/taskManager/forgot_password/](http://127.0.0.1:8000/taskManager/forgot_password/) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/taskManager/tutorials/misconfig/](http://127.0.0.1:8000/taskManager/tutorials/misconfig/) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/taskManager/tutorials/idor/](http://127.0.0.1:8000/taskManager/tutorials/idor/) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/taskManager/login/](http://127.0.0.1:8000/taskManager/login/) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/taskManager/tutorials/redirects/](http://127.0.0.1:8000/taskManager/tutorials/redirects/) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/robots.txt](http://127.0.0.1:8000/robots.txt) + + + * Method: `GET` + + + * Parameter: `X-XSS-Protection` + + + + +* URL: [http://127.0.0.1:8000/taskManager/forgot_password/](http://127.0.0.1:8000/taskManager/forgot_password/) + + + * Method: `POST` + + + * Parameter: `X-XSS-Protection` + + + + +Instances: 23 + +### Solution +Ensure that the web browser's XSS filter is enabled, by setting the X-XSS-Protection HTTP response header to '1'.
+ +### Other information +The X-XSS-Protection HTTP response header allows the web server to enable or disable the web browser's XSS protection mechanism. The following values would attempt to enable it:
X-XSS-Protection: 1; mode=block
X-XSS-Protection: 1; report=http://www.example.com/xss
The following values would disable it:
X-XSS-Protection: 0
The X-XSS-Protection HTTP response header is currently supported on Internet Explorer, Chrome and Safari (WebKit).
Note that this alert is only raised if the response body could potentially contain an XSS payload (with a text-based content type, with a non-zero length).
+ +### Reference +* https://www.owasp.org/index.php/XSS_(Cross_Site_Scripting)_Prevention_Cheat_Sheet +* https://blog.veracode.com/2014/03/guidelines-for-setting-security-headers/ + + +#### CWE Id : 933 + +#### WASC Id : 14 + +#### Source ID : 3 + + + + +### X-Content-Type-Options Header Missing +##### Low (Medium) + + + + +#### Description +The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.
+ + + +* URL: [http://127.0.0.1:8000/taskManager/tutorials/access/](http://127.0.0.1:8000/taskManager/tutorials/access/) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/taskManager/register/](http://127.0.0.1:8000/taskManager/register/) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/taskManager/login/](http://127.0.0.1:8000/taskManager/login/) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/static/taskManager/css/bootstrap.min.css](http://127.0.0.1:8000/static/taskManager/css/bootstrap.min.css) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/static/taskManager/js/backend/jquery.dcjqaccordion.2.7.js](http://127.0.0.1:8000/static/taskManager/js/backend/jquery.dcjqaccordion.2.7.js) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/static/taskManager/js/backend/slidebars.min.js](http://127.0.0.1:8000/static/taskManager/js/backend/slidebars.min.js) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/static/taskManager/js/backend/jquery.customSelect.min.js](http://127.0.0.1:8000/static/taskManager/js/backend/jquery.customSelect.min.js) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/taskManager/tutorials/misconfig/](http://127.0.0.1:8000/taskManager/tutorials/misconfig/) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/static/taskManager/js/bootstrap.js](http://127.0.0.1:8000/static/taskManager/js/bootstrap.js) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/taskManager/tutorials/brokenauth/](http://127.0.0.1:8000/taskManager/tutorials/brokenauth/) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/taskManager/tutorials/redirects/](http://127.0.0.1:8000/taskManager/tutorials/redirects/) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000](http://127.0.0.1:8000) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/static/taskManager/css/font-awesome.css](http://127.0.0.1:8000/static/taskManager/css/font-awesome.css) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/taskManager/forgot_password/](http://127.0.0.1:8000/taskManager/forgot_password/) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/taskManager/tutorials/idor/](http://127.0.0.1:8000/taskManager/tutorials/idor/) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/static/taskManager/js/backend/respond.min.js](http://127.0.0.1:8000/static/taskManager/js/backend/respond.min.js) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/taskManager/forgot_password/](http://127.0.0.1:8000/taskManager/forgot_password/) + + + * Method: `POST` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/static/taskManager/css/backend/bootstrap-reset.css](http://127.0.0.1:8000/static/taskManager/css/backend/bootstrap-reset.css) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/static/taskManager/css/railscasts.css](http://127.0.0.1:8000/static/taskManager/css/railscasts.css) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +* URL: [http://127.0.0.1:8000/static/taskManager/img/logo_lg.png](http://127.0.0.1:8000/static/taskManager/img/logo_lg.png) + + + * Method: `GET` + + + * Parameter: `X-Content-Type-Options` + + + + +Instances: 41 + +### Solution +Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.
If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.
+ +### Other information +This issue still applies to error type pages (401, 403, 500, etc) as those pages are often still affected by injection issues, in which case there is still concern for browsers sniffing pages away from their actual content type.
At "High" threshold this scanner will not alert on client or server error responses.
+ +### Reference +* http://msdn.microsoft.com/en-us/library/ie/gg622941%28v=vs.85%29.aspx +* https://www.owasp.org/index.php/List_of_useful_HTTP_headers + + +#### CWE Id : 16 + +#### WASC Id : 15 + +#### Source ID : 3 + + + + +### Cookie No HttpOnly Flag +##### Low (Medium) + + + + +#### Description +A cookie has been set without the HttpOnly flag, which means that the cookie can be accessed by JavaScript. If a malicious script can be run on this page then the cookie will be accessible and can be transmitted to another site. If this is a session cookie then session hijacking may be possible.
+ + + +* URL: [http://127.0.0.1:8000/taskManager/register/](http://127.0.0.1:8000/taskManager/register/) + + + * Method: `GET` + + + * Parameter: `csrftoken` + + + * Evidence: `Set-Cookie: csrftoken` + + + + +* URL: [http://127.0.0.1:8000/taskManager/login/](http://127.0.0.1:8000/taskManager/login/) + + + * Method: `GET` + + + * Parameter: `csrftoken` + + + * Evidence: `Set-Cookie: csrftoken` + + + + +* URL: [http://127.0.0.1:8000/taskManager/forgot_password/](http://127.0.0.1:8000/taskManager/forgot_password/) + + + * Method: `POST` + + + * Parameter: `messages` + + + * Evidence: `Set-Cookie: messages` + + + + +* URL: [http://127.0.0.1:8000/taskManager/login/](http://127.0.0.1:8000/taskManager/login/) + + + * Method: `POST` + + + * Parameter: `csrftoken` + + + * Evidence: `Set-Cookie: csrftoken` + + + + +* URL: [http://127.0.0.1:8000/taskManager/register/](http://127.0.0.1:8000/taskManager/register/) + + + * Method: `POST` + + + * Parameter: `csrftoken` + + + * Evidence: `Set-Cookie: csrftoken` + + + + +Instances: 5 + +### Solution +Ensure that the HttpOnly flag is set for all cookies.
+ +### Reference +* http://www.owasp.org/index.php/HttpOnly + + +#### CWE Id : 16 + +#### WASC Id : 13 + +#### Source ID : 3 + + + + +### Password Autocomplete in Browser +##### Low (Medium) + + + + +#### Description +The AUTOCOMPLETE attribute is not disabled on an HTML FORM/INPUT element containing password type input. Passwords may be stored in browsers and retrieved.
+ + + +* URL: [http://127.0.0.1:8000/taskManager/register/](http://127.0.0.1:8000/taskManager/register/) + + + * Method: `GET` + + + * Parameter: `id_password` + + + * Evidence: `` + + + + +* URL: [http://127.0.0.1:8000/taskManager/login/](http://127.0.0.1:8000/taskManager/login/) + + + * Method: `GET` + + + * Parameter: `password` + + + * Evidence: `` + + + + +* URL: [http://127.0.0.1:8000/taskManager/login/](http://127.0.0.1:8000/taskManager/login/) + + + * Method: `POST` + + + * Parameter: `password` + + + * Evidence: `` + + + + +* URL: [http://127.0.0.1:8000/taskManager/register/](http://127.0.0.1:8000/taskManager/register/) + + + * Method: `POST` + + + * Parameter: `id_password` + + + * Evidence: `` + + + + +Instances: 4 + +### Solution +Turn off the AUTOCOMPLETE attribute in forms or individual input elements containing password inputs by using AUTOCOMPLETE='OFF'.
+ +### Reference +* http://www.w3schools.com/tags/att_input_autocomplete.asp +* https://msdn.microsoft.com/en-us/library/ms533486%28v=vs.85%29.aspx + + +#### CWE Id : 525 + +#### WASC Id : 15 + +#### Source ID : 3