25 September 2008 | 33,211 views

BSQL Hacker – Automated SQL Injection Framework

Acunetix Web Application Security

BSQL Hacker is an automated SQL Injection Framework / Tool designed to exploit SQL injection vulnerabilities in virtually any database.

It ships with Automated Attack modules which allows the dumping of whole databases for the following DBMS:

  • MS-SQL Server
  • ORACLE
  • MySQL (experimental)

Attack Templates for:

  • MS Access
  • MySQL
  • ORACLE
  • PostgreSQL
  • MS-SQL Server

Also you can write your own attack template for any other database as well (see the manual for details). New attack templates and exploits for specific web application can be shared via Exploit Repository.

BSQL Hacker aims for experienced users as well as beginners who want to automate SQL Injections (especially Blind SQL Injections).

It supports :

  • Blind SQL Injection (Boolean Injection)
  • Full Blind SQL Injection (Time Based)
  • Deep Blind SQL Injection (a new way to exploit BSQLIs, explained here)
  • Error Based SQL Injection

It allows metasploit alike exploit repository to share and update exploits and attack temlpates.

You can download BSQL Hacker here:

BSQLHackerSetup-0907.exe

Or read more here.





                

Recent in Database Hacking:
- 1 Million Accounts Leaked From Banks, Government Agencies & Consultancy Firms
- The Mole v0.3 Released For Download – Automatic SQL Injection Exploitation Tool
- MySQL 1 Liner Hack Gives Root Access Without Password

Related Posts:
- Havij – Advanced Automated SQL Injection Tool
- FG-Injector – SQL Injection & Proxy Tool
- w3af – Web Application Attack and Audit Framework

Most Read in Database Hacking:
- Pangolin – Automatic SQL Injection Tool - 67,146 views
- bsqlbf 1.1 – Blind SQL Injection Tool - 53,589 views
- Absinthe Blind SQL Injection Tool/Software - 38,717 views

Advertise on Darknet

4 Responses to “BSQL Hacker – Automated SQL Injection Framework”

  1. Yami King 30 September 2008 at 5:54 pm Permalink

    The tool itself is quite nice -though it still crashes sometimes over here- and can be proven useful in many situations. Especially the template functionality is timeless, not only for novices, but also for many people just trying to be productive.

    But there is one thing I dislike about these kinds of products, and it has something to do with the fact I just said the template functionality is timeless… That is, that these tools should not be necessary anymore, especially not since the SQL Injection and it’s relatives (Blind SQL Injection, Deep Blind SQL Injection, etc..) are one of the most discussed and documented (web)application vulnerabilities out there.

  2. SpikyHead 2 October 2008 at 2:19 am Permalink

    Ididnt get a chance to check out the tools as yet..

    @Yami
    I disagree, such tools are still very much needed. especially for security consultants to show the power of sql injection… or for security audits..

    as well as for security new bees

  3. Yami King 2 October 2008 at 10:24 am Permalink

    @ SpikyHead
    You are correct about the fact that these tools can still be useful and even necessary for security consultants and auditers.
    But my comment was especially aimed at the fact that there are still a lot of (web)applications vulnerable to SQL Injections, while it is one of the most documented attack around, and this should not be the case.

    The following is a bit abstract (maybe a bit too abstract) but I think you’ll get the basic idea of what I meant:
    `Instead of making tools to test for SQL Injection vulnerabilities, make the application invulnerable to SQL Injections.`
    Though there is a sort of chicken and the egg problem here, since you need to test your application for SQL Injections to prove it is invulnerable, but that’s not the point I wanted to make.

  4. SpikyHead 3 October 2008 at 7:02 am Permalink

    @Yami King
    I got that now.. yeah, I agree with you on this. preach secure coding day and night. But, the day is still very far away when applications will be invulnerable to such attacks… as still 99% of the developers are more focused towards features and performance on the cost of security issues.

    Till that day, these tools will help us earn our bread. ;)