The challenges we’re going to solve are the following:
Log into the application as firstname.lastname@example.org
Log into the application as email@example.com
Log into the application as firstname.lastname@example.org
Going to the application let’s go to the login page – screenshot:
Reviewing the objectives we have the username (email), but we don’t have the password… Meaning we can’t log into the application… well let’s see.
We already know the application is buggy (our favorite!) so it will not be hard to deduce that the application is not sanitizing our input. Meaning we can append certain characters in the username box and bypass entering a password to log into the application.
What possibly are these characters?
We know that for a valid login there has to be an back-end database that is used to test the username and password. We have the username, but what if we trick the database with a true statement and allow us to log into the application without entering a password.
The topic that I am talking about is SQL Injection. Doing a Google search you will see there are plenty websites dedicated to this topic.
Let’s imagine that the back-end database is the following:
SELECT valid_login FROM customers WHERE username=uname AND password=passwd;
Note: valid_login will return a boolean (TRUE/FALSE)
The username is the email that we have plus the appended characters –> email@example.com’ OR ‘1’=’1
Password is going to be blank.
So the above line will be:
SELECT valid_login FROM customers WHERE username=’firstname.lastname@example.org’ OR ‘1’=’1 AND password=<blank>;
The password is going to be blank.
Let’s break down the above statement
We’re closing the email@example.com expression, and then we’re going to include a new expression using the OR statement. The next expression is 1=1 which will ALWAYS evaluate to true (1 does equal 1).
Try it in the application and see what happens.
First, let’s configure our browser to listen through our Burp proxy.
Going to the login page, let’s add the username of firstname.lastname@example.org’ OR ‘1’=’1′, with no password, and press the Login button.
We’ve successfully logged in without a valid password!
Let’s see if we can do this with the second username: email@example.com
We were able to log into the application as user1, without supplying a valid password!
Let’s try username: firstname.lastname@example.org
Going back to the login page, let’s enter the username as email@example.com without supplying a password.
We were able to log into the application as an admin without supplying a valid password.
Hmm… we see with the admin login we have a new link – Comments. We’ll come back to this in another post.
Going back to the scoreboard we see:
All of the login challenges are now complete (green)!
This post will be a first in a series to solve the BodgeIt Store.
I am running the BodgeIt store from an ISO (disk image) on a virtual machine (I am using VM Workstation Player 12 which is free). I have a previous post that describes how to install ISO’s in virtual machines (VMs). Link here.
Now on to the hacking!
After installing the ISO, and powering on the VM, you will be presented with the login page:
Navigating to the IP you will see OWASP BWA (Broken Web Application) homepage:
Clicking on the BodgeIt link we’re presented with this homepage:
Going to the “About Us” we see there’s a scoring page.
Clicking on the scoring page, we see:
By the end of the series, these challenges will be green (completed).
Let’s get started!
I’m going to start with “Level 1: Display a popup using: alert(“XSS”)”
Note: I am using Google Chrome which has XSS auditor pre-installed in the application.
If you’re using Chrome you will need to temporarily disable this for the XSS vulnerability. Make sure to close ALL instances of Chrome before entering the below command.
To disable xss auditor, open a command prompt (run –> cmd.exe), and enter (or copy) the following: “C:\Program Files (x86)\Google\Chrome\Application\chrome.exe” –disable-xss-auditor
Once you press Enter, a new instance of Chrome will open.
OK, now a new instance of Chrome has opened, and we’ve navigated to the BodgeIt store.
Going to the Search link we see the following:
Entering the following line in the search input: alert(“XSS”)
And pressing the “Search” button we see:
We have successfully simulated a XSS attack!
Navigating back to the scoring page (About Us –> Scoring Page) we see:
You must be logged in to post a comment.