Wapiti – Web Application Vulnerability Scanner v2.3.0


Wapiti is a web application vulnerability scanner, it allows you to audit the security of your web applications. It performs “black-box” scans, i.e. it does not study the source code of the application but will scans the web pages of the deployed web application, looking for scripts and forms where it can inject data.

Once it gets this list, Wapiti acts like a fuzzer, injecting payloads to see if a script is vulnerable.

Wapiti - Web Application Vulnerability Scanner v2.3.0

We first wrote about Wapiti WAYYY back in 2006 – Wapiti – Web Application Scanner / Black-box testing. It’s come a long way since then, but there doesn’t seem to be much active development since 2013 – which is a shame as it’s a good tool.

Wapiti can detect the following vulnerabilities :

  • File disclosure (Local and remote include/require, fopen, readfile…)
  • Database Injection (PHP/JSP/ASP SQL Injections and XPath Injections)
  • XSS (Cross Site Scripting) injection (reflected and permanent)
  • Command Execution detection (eval(), system(), passtru()…)
  • CRLF Injection (HTTP Response Splitting, session fixation…)
  • XXE (XmleXternal Entity) injection
  • Use of know potentially dangerous files (thanks to the Nikto database)
  • Weak .htaccess configurations that can be bypassed
  • Presence of backup files giving sensitive information (source code disclosure)

Features

  • Generates vulnerability reports in various formats (HTML, XML, JSON, TXT…)
  • Can suspend and resume a scan or an attack
  • Can give you colors in the terminal to highlight vulnerabilities
  • Different levels of verbosity
  • Fast and easy way to activate/deactivate attack modules
  • Adding a payload can be as easy as adding a line to a text file
  • Supports both GET and POST HTTP methods for attacks
  • It also supports multipart and can inject payloads in filenames (upload)
  • Display a warning when an anomaly is found (for example 500 errors and timeouts)
  • Makes the difference beetween permanent and reflected XSS vulnerabilities.

You can download Wapiti v2.3.0 here:

Windowswapiti-2.3.0-win32-standalone.zip
Linuxwapiti-2.3.0.tar.gz

Or read more here.

Posted in: Hacking Tools, Web Hacking

, , , ,


Latest Posts:


Nipe - Make Tor Default Gateway For Network Nipe – Make Tor Default Gateway For Network
Nipe is a Perl script to make Tor default gateway for network, this script enables you to directly route all your traffic from your computer to the Tor network.
Mosca - Manual Static Analysis Tool To Find Bugs Mosca – Manual Static Analysis Tool To Find Bugs
Mosca is a manual static analysis tool written in C designed to find bugs in the code before it is compiled, much like a grep unix command.
Slurp - Amazon AWS S3 Bucket Enumerator Slurp – Amazon AWS S3 Bucket Enumerator
Slurp is a blackbox/whitebox S3 bucket enumerator written in Go that can use a permutations list to scan externally or an AWS API to scan internally.
US Government Cyber Security Still Inadequate US Government Cyber Security Still Inadequate
Surprise, surprise, surprise - an internal audit of the US Government cyber security situation has uncovered widespread weaknesses, legacy systems and poor adoption of cyber controls and tooling.
BloodHound - Hacking Active Directory Trust Relationships BloodHound – Hacking Active Directory Trust Relationships
BloodHound is for hacking active directory trust relationships and it uses graph theory to reveal the hidden and often unintended relationships within an AD environment.
SecLists - Usernames, passwords, URLs, sensitive data patterns, fuzzing payloads, web shells SecLists – Usernames, passwords, URLs, sensitive data patterns, fuzzing payloads, web shells
SecLists is the security tester's companion. It's a collection of multiple types of lists used during security assessments, collected in one place.


2 Responses to Wapiti – Web Application Vulnerability Scanner v2.3.0

  1. poto May 11, 2015 at 7:00 am #

    Why mention the tool if it was abandoned?
    Feeling nostalgic again?

    • Darknet May 11, 2015 at 7:10 pm #

      Because it’s still good, and there’s been a lot of improvements since our last post about it in 2006. Perhaps with some attention, they might start development again..