Absinthe Blind SQL Injection Tool/Software


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:


Aclpwn.Py - Exploit ACL Based Privilege Escalation Paths in Active Directory Aclpwn.Py – Exploit ACL Based Privilege Escalation Paths in Active Directory
Aclpwn.py is a tool that interacts with BloodHound< to identify and exploit ACL based privilege escalation paths.
Vulhub - Pre-Built Vulnerable Docker Environments For Learning To Hack Vulhub – Pre-Built Vulnerable Docker Environments For Learning To Hack
Vulhub is an open-source collection of pre-built vulnerable docker environments for learning to hack. No pre-existing knowledge of docker is required, just execute two simple commands.
LibInjection - Detect SQL Injection (SQLi) and Cross-Site Scripting (XSS) LibInjection – Detect SQL Injection (SQLi) and Cross-Site Scripting (XSS)
LibInjection is a C library to Detect SQL Injection (SQLi) and Cross-Site Scripting (XSS) through lexical analysis of real-world Attacks.
Grype - Vulnerability Scanner For Container Images & Filesystems Grype – Vulnerability Scanner For Container Images & Filesystems
Grype is a vulnerability scanner for container images and filesystems with an easy to install binary that supports the packages for most major *nix based OS.
APT-Hunter - Threat Hunting Tool via Windows Event Log APT-Hunter – Threat Hunting Tool via Windows Event Log
APT-Hunter is a threat hunting tool for windows event logs made from the perspective of the purple team mindset to provide detection for APT movements hidden in the sea of windows event logs.
GitLab Watchman - Audit Gitlab For Sensitive Data & Credentials GitLab Watchman – Audit Gitlab For Sensitive Data & Credentials
GitLab Watchman is an app that uses the GitLab API to audit GitLab for sensitive data and credentials exposed internally, this includes code, commits, wikis etc


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.