Absinthe is a gui-based tool that automates the process of downloading the schema & contents of a database that is vulnerable to Blind SQL Injection.
Absinthe does not aid in the discovery of SQL Injection holes. This tool will only speed up the process of data recovery.
Features:
- Automated SQL Injection
- Supports MS SQL Server, MSDE, Oracle, Postgres
- Cookies / Additional HTTP Headers
- Query Termination
- Additional text appended to queries
- Supports Use of Proxies / Proxy Rotation
- Multiple filters for page profiling
- Custom Delimiters
More Information here:
Subscribe to Darknet RSS Feed Stored in: Database Hacking, Hacking Tools, Web Hacking
Related Posts:
- Bsqlbf V2 – Blind SQL Injection Brute Forcer Tool
- FG-Injector – SQL Injection & Proxy Tool
- BSQL Hacker – Automated SQL Injection Framework
- bsqlbf v2.3 Released – Blind SQL Injection Brute Forcing Tool
- bsqlbf 1.1 – Blind SQL Injection Tool
- SQLBrute – SQL Injection Brute Force Tool
| 22,889 views |
thank u
thanks
hi,
i’m a newbie into this world of hacking and i’m trying to get as much information as i can about it.your website’s really educational and self explanantory but i haven’t had enough time to view the entire website as much as i would like to.
i would love to know more about the basics of hacking ie the do’s and don’ts of hacking,database hacking,how to discover exploits and the best ways of penetration.i am in a country where there’s not much to information technology so i’m free to exploit my horizons.i want you guys reading this comment to pls help me.my private email is clementcoles@yahoo.com.
thank you.
Very Tnx !
This program SUCKS ! don’t use it, plus it sends your SQL inj to the developer server, and god knows what he do with the data !
Blindness is one of the side-effects of major absinthe indulgence indeed.
sound like a great tool but there has to be a way around the particular issue that snap mentioned. for sure there is something that could be done.
Maybe it’s used to harvest data on what type of attacks are being used, so they can be patched up.
If it’s sending the data to the developer, then there’d be something in the code that details that. ie – you’d need to edit the source and remove that bit. But – why wouldn’t you want the developer of opensource ware getting details back on your useage of their tool – unless it was being used for something bad!
Of course, I’m going on the premise of info-sharing there, and not on the premise that it’s a bad thing that is harvesting data on people so it can hijack their machines or something like that.
if i am using it to pentest my own system maybe i don’t want them to know about the holes in my system let them keep their collective noses out of my business.