Automate your XSS tests with Selenium
We are heading into an era where potential attackers have very easy knowledge access. In some instances proper training isn’t even required, because offensive tools are getting better and better. A lot of companies decided that it’s better to pay real money for security bugs (see Bug Bounty list) than take a risk hostile exposure.
As testers we shouldn’t ignore this trend. This is already reflected in job offers - you may often notice that defensive/offensive security knowledge is starting to appear not only in ‘nice to have’ section, but also in requirements. I have already made 2 posts about various security testing aspects.
XSS (cross-site scripting) is one of the easiest vulnerabilities to test (for example by scanners). It’s also the second most prevalent issue in the OWASP Top 10, and is found in around two thirds of all applications. Today I want to show you how to test against XSS using Selenium. We would focus our attention on the most popular and common type of XSS - Reflected Cross-Site Scripting.
Reflected Cross-Site Scripting basics
OWASP provides excellent description of Reflected XSS which doesn’t require much explanation:
These holes show up when data provided by a web client is used immediately by server-side scripts to generate a page of results for that user. If unvalidated user-supplied data is included in the resulting page without HTML encoding, this will allow client-side code to be injected into the dynamic page. A classic example of this is in site search engines: if one searches for a string which includes some HTML special characters, often the search string will be redisplayed on the result page to indicate what was searched for, or will at least include the search terms in the text box for easier editing. If all occurrences of the search terms are not HTML entity encoded, an XSS hole will result.__
For more information see OWASP Testing Guide which is amazing resource available for free.
Example in Java
As usual I enjoyed the most coding part. I commited it on my Github project.
Let’s split the explanation into few parts:
This step can be omitted entirely if you are using Firefox. I usually prefer Chrome (chromedriver is in my opinion the most reliable driver) so I had to disable built-in client xss protection first. I have already covered it extensively in my Browser Capabilites Explained post so I assume reader doesn’t require additional explanation.
XSS protection in Google Chrome is disabled by_--disable-xss-auditor_ option.
Picking a vulnerable page
Obviously in order to show you how to test against XSS I had to find a vulnerable page. I decided to use XSS game level 1.
That’s the Page Object implementation using FluentLenium.
Having Page Object implemented we are ready for testing. Here is complete code of my test:
As you can see there is weirdly lookin CSS_CONTENT string which require further explanation:
Usually we want our test to have clear success/failure criteria. That’s why I implemented the following method in my PageObject:
This method is returning true if popup is displayed in 2 seconds time.
Execute the test on your computer and you will see that it fails - we have found XSS!