tP CONFIGTORPORT, -tor-port CONFIGTORPORTĬhange the port that Tor runs on (*default=9050) Send requests in parallel (specify number of threads (*default=1) Send this data with the POST request (*default=random) P, -post Send a POST request (*default=GET) timeout TIMEOUT Control the timeout time of the requests (*default=15) Provide a sleep time per request (*default=0) force-ssl Force the assignment of HTTPS instead of HTTP while processing (*default=HTTP unless otherwise specified by URL) Provide a file containing a list of payloads 1 per line
Provide your own payloads separated by a comma IE AND 1=1,AND 2=2 check-tor Check your Tor connection (default=False)
tor Use Tor as the proxy to run behind, must have Tor installed (*default=False) proxy PROXY Provide a proxy to run behind in the format type://address:port (IE socks5://10.54.127.4:1080) (*default=None) Your headers need to be exact(IE: Set-Cookie=a345ddsswe,X-Forwarded-For:127.0.0.1) (*default=None) To use multiple separate headers by comma. H HEADER=VALUE,HEADER:VALUE., -headers HEADER=VALUE,HEADER:VALUE.Īdd your own custom headers to the request. ra Use a random user-agent for the HTTP requests (*default=whatwaf/2.0.3 (Language=3.9.2 Platform=Linux)) pa USER-AGENT Provide your own personal agent to use it for the HTTP requests Pass a JSON file from the Googler CMD line tool (IE googler -n 100 -json > googler.json)Īrguments that will control your requests g GOOGLER-JSON-FILE, -googler GOOGLER-JSON-FILE Pass a Burp Suite request file to perform WAF evaluation Pass a file containing URL's (one per line) to detect the protection u URL, -url URL Pass a single URL to detect the protection h, -help show this help message and exitĪrguments that have to be passed for the program to run whatwaf - VALUE|PATH|PATH|PATH PAYLOAD.|PATH WebKnight Application Firewall (AQTRONIX) Stingray Application Firewall (Riverbed/Brocade) Open Source Web Application Firewall (Modsecurity) Incapsula Web Application Firewall (Incapsula/Imperva) XSS/CSRF Filtering Protection (CodeIgniter)ĭeny All Web Application Firewall (DenyAll)ĭoD Enterprise-Level Protection System (Department of Defense)ĮdgeCast Web Application Firewall (Verizon)įortiWeb Web Application Firewall (Fortinet) Yunjiasu Web Application Firewall (Baidu)īarracuda Web Application Firewall (Barracuda Networks)īinarySEC Web Application Firewall (BinarySEC)Ĭhuangyu top government cloud defense platform (WAF)ĬloudFlare Web Application Firewall (CloudFlare) List of all web application security systems supported for identification, WAF (89 in total):ĪkamaiGHost Website Protection (Akamai Global Host)Īnquanbao Web Application Firewall (Anquanbao)ĪnYu Web Application Firewall (Anyu Technologies)Īpplication Security Manager (F5 Networks)ĪSP.NET Generic Website Protection (Microsoft)Īmazon Web Services Web Application Firewall (Amazon) WhatWaf is an advanced web application security detection tool that aims to give you an answer to the question, “Does a web server use WAF, and which one?” WhatWaf works by detecting a firewall on a web application, and attempting to detect a bypass (or two) for said firewall, on the specified target.Ībility to run on a single URL with the -u/ -url flagĪbility to run through a list of URL's with the -l/ -list flagĪbility to detect over 70+ different firewallsĪbility to try over 30+ different tampering techniquesĪbility to pass your own payloads either from a file, from the terminal, or use the default payloadsĭefault payloads that should produce at least one WAF triggeringĪbility to bypass firewalls using both SQLi techniques and cross site scripting techniquesĪbility to run behind any proxy type that matches this regex: (socks\d+)?(http(s)?)?:// (socks5, socks4, http, https)Ībility to use a random user agent, personal user agent, or custom default user agentĪuto assign protocol to HTTP or ability to force protocol to HTTPSĪ built in encoder so you can encode your payloads into the discovered bypassesĪutomatic issue creation if an unknown firewall is discoveredĪbility to send output to a JSON, CSV, or YAML fileĪbility to encode provided payloads using builtin tamper scriptsĮncoded payloads are then saved into a database file for future useĪbility to export cached payloads from the database to a YAML, JSON, CSV, or textual fileĪbility to save all traffic into files for further analysis by passing the -traffic flagĪbility to try and determine the backend webserver hosting the web application using -WĪbility to pass in your own custom headers
0 kommentar(er)
