WAF Bypass Tool v1.18 releases: open source tool to analyze the security of any WAF

WAF Bypass Tool

WAF bypass Tool is an open-source tool to analyze the security of any WAF for False Positives and False Negatives using predefined and customizable payloads. Check your WAF before an attacker does. WAF Bypass Tool is developed by the Nemesida WAF team with the participation of the community.

Payloads

Depending on the purpose, payloads are located in the appropriate folders:

• FP – False Positive payloads
• API – API testing payloads
• CM – Custom HTTP Method payloads
• GraphQL – GraphQL testing payloads
• LDAP – LDAP Injection etc. payloads
• LFI – Local File Include payloads
• MFD – multipart/form-data payloads
• NoSQLi – NoSQL injection payloads
• OR – Open Redirect payloads
• RCE – Remote Code Execution payloads
• RFI – Remote File Inclusion payloads
• SQLi – SQL injection payloads
• SSI – Server-Side Includes payloads
• SSRF – Server-side request forgery payloads
• SSTI – Server-Side Template Injection payloads
• UWA – Unwanted Access payloads
• XSS – Cross-Site Scripting payloads

Write your own payloads

When compiling a payload, the following zones, methods, and options are used:

• URL – request’s path
• ARGS – request’s query
• BODY – request’s body
• COOKIE – request’s cookie
• USER-AGENT – request’s user-agent
• REFERER – request’s referer
• HEADER – request’s header
• METHOD – request’s method
• BOUNDARY – specifies the contents of the request’s boundary. Applicable only to payloads in the MFD directory.
• ENCODE – specifies the type of payload encoding (Base64, HTML-ENTITY, UTF-16) in addition to the encoding for the payload. Multiple values are indicated with a space (e.g. Base64 UTF-16). Applicable only to for ARGS, BODY, COOKIE and HEADER zone. Not applicable to payloads in API and MFD directories. Not compatible with option JSON.
• JSON – specifies that the request’s body should be in JSON format
• BLOCKED – specifies that the request should be blocked (FN testing) or not (FP)

Except for some cases described below, the zones are independent of each other and are tested separately (if 2 zones are specified – the script will send 2 requests – alternately checking one and the second zone).

For the zones you can use %RND% suffix, which allows you to generate an arbitrary string of 6 letters and numbers. (e.g.: param%RND=my_payload or param=%RND% OR A%RND%B)

You can create your own payloads, to do this, create your own folder on the ‘/payload/’ folder, or place the payload in an existing one (e.g.: ‘/payload/XSS’). Allowed data format is JSON.

API directory

API testing payloads located in this directory are automatically appended with a header 'Content-Type: application/json'.

MFD directory

For MFD (multipart/form-data) payloads located in this directory, you must specify the BODY (required) and BOUNDARY (optional). If BOUNDARY is not set, it will be generated automatically (in this case, only the payload must be specified for the BODY, without additional data ('... Content-Disposition: form-data; ...').

If a BOUNDARY is specified, then the content of the BODY must be formatted in accordance with the RFC, but this allows for multiple payloads in BODY a separated by BOUNDARY.

Other zones are allowed in this directory (e.g.: URL, ARGS etc.). Regardless of the zone, header 'Content-Type: multipart/form-data; boundary=...' will be added to all requests.

Changelog v1.1.8

• Encoding fix

Install & Use

Copyright (c) 2020 Pentestit LLC