Mutillidae - Blind SQL via Timing (User Lookup)

Mutillidae – Blind SQL via Timing (User Lookup)

In this walk through, we will be going through the Blind SQL via Timing (User Lookup) vulnerability section from Mutillidae Labs. We will be exploring and exploiting Blind SQL Injection via Timing attacks on User Lookup utility and learn how application are affected because of it. So, let’s get started with the Hacking without any delay.

Blind SQL via Timing (User Lookup)

Security Level: 0 (Hosed)

  • Setting the security level to 0 or Hosed.

Security level 0

  • The application as a User Lookup functionality which demands a pair of credentials to view the user data.

User Lookup (SQL)

  • I used the below payload to dump all the user information in the DB.

' OR 1=1-- -

Dumping all data

Also Read: Mutillidae – Authentication Bypass (Cookies)



So, we finally completed all the security levels for the Blind SQL via Timing (User Lookup) 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”.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top