In this walk through, we will be going through the SQLi Insert Injection (View Captured Data) vulnerability section from Mutillidae Labs. We will be exploring and exploiting SQL Injection in Capture Data page and learn how application are affected because of it. So, let’s get started with the Hacking without any delay.
Table of Contents
Security Level: 0 (Hosed)
- Setting the security level to 0 or Hosed.
- The application shows the captured data from the captured-data.php page. The designated page captures the useragent and other HTTP header information and displays on page.
- I intercepted the below request of capture-data.php file and changed the User-Agent to “Hello Again”. On forwarding the request and refreshing our challenge page shows our entry.
- Next, i inserted an apostrophe in User-Agent field and it displays an error. This might indicate that application is vulnerable to SQLi.
- Exploited the SQLi using sqlmap.
sqlmap -u http://localhost/mutillidae/index.php?page=capture-data.php --cookie="showhints=1; PHPSESSID=3rcd9jem7elt5mqahbh27pca34" -p User-Agent --dbs
Also Read: Mutillidae – SQLi Insert Injection (Add to your blog)
Conclusion:
So, we finally completed all the security levels for the Mutillidae SQLi Insert Injection (View Captured Data) Vulnerability. We looked into the various ways how application has been set up in various levels and how we can bypass the security controls implemented. Next, we can mitigate the potential SQL Injection attacks by performing input sanitization and using prepared statements or parametrized queries for every SQL query made by the application to the database. On that note, i will take your leave and will meet you in next one with another Mutillidae vulnerability writeup, till then “Keep Hacking”.
