Absinthe Blind SQL Injection Tool/Software

Use Netsparker


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:

Absinthe (Documentation)

Posted in: Database Hacking, Hacking Tools, Web Hacking

, , ,


Latest Posts:


Eraser - Windows Secure Erase Hard Drive Wiper Eraser – Windows Secure Erase Hard Drive Wiper
Eraser is a hard drive wiper for Windows which allows you to run a secure erase and completely remove sensitive data from your hard drive by overwriting it several times with carefully selected patterns.
Insecure software versions are a problem Web Security Stats Show XSS & Outdated Software Are Major Problems
Netsparker just published some anonymized Web Security Stats about the security vulnerabilities their online solution identified on their users’ web applications and web services during the last 3 years.
CTFR - Abuse Certificate Transparency Logs For HTTPS Subdomains CTFR – Abuse Certificate Transparency Logs For HTTPS Subdomains
CTFR is a Python-based tool to Abuse Certificate Transparency Logs to get subdomains from a HTTPS website in a few seconds.
testssl.sh - Test SSL Security Including Ciphers, Protocols & Detect Flaws testssl.sh – Test SSL Security Including Ciphers, Protocols & Detect Flaws
testssl.sh is a free command line tool to test SSL security, it checks a server's service on any port for the support of TLS/SSL ciphers, protocols as well as recent cryptographic flaws and more.
Four Year Old libSSH Bug Leaves Servers Wide Open Four Year Old libssh Bug Leaves Servers Wide Open
A fairly serious 4-year old libssh bug has left servers vulnerable to remote compromise, fortunately, the attack surface isn't that big as neither OpenSSH or the GitHub implementation are affected.
CHIPSEC - Platform Security Assessment Framework CHIPSEC – Platform Security Assessment Framework For Firmware Hacking
CHIPSEC is a platform security assessment framework for PCs including hardware, system firmware (BIOS/UEFI), and platform components for firmware hacking.


9 Responses to Absinthe Blind SQL Injection Tool/Software

  1. brave July 4, 2006 at 11:27 am #

    thank u

  2. Anh July 10, 2006 at 2:32 am #

    thanks

  3. clement August 9, 2006 at 12:35 pm #

    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.

  4. Ahmad September 8, 2006 at 12:43 pm #

    Very Tnx !

  5. Snap April 16, 2008 at 7:46 am #

    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 !

  6. zupakomputer April 16, 2008 at 1:53 pm #

    Blindness is one of the side-effects of major absinthe indulgence indeed.

  7. fever April 17, 2008 at 4:30 am #

    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.

  8. zupakomputer April 17, 2008 at 3:44 pm #

    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.

  9. fever April 19, 2008 at 6:49 am #

    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.