Content rule to block XSS attack <script> tags in URL
Information
Summary: |
This article outlines a solution for blocking XSS attack <script> tags in defined URLs and returning a 403 Forbidden error message. |
Environment: |
Product: LoadMaster Version: Any Platform: Any Application: Any |
Question/Problem Description: |
How to block XSS attack <script> tags in defined URLs on the LoadMaster using a single content rule? |
Steps to Reproduce: | |
Error Message: | |
Defect Number: | |
Enhancement Number: | |
Cause: | |
Resolution: |
Below is an example syntax for a content rule that blocks XSS attack <script> tags in defined URLs:
Rule Name: block_XSS
After creating the above content rule, it is then necessary to apply it under a Virtual Service or Sub Virtual Service (SubVS) as a HTTP Selection rule under Advanced Properties. Then under the same Advanced Properties, set the Not Available Redirection Handling to 403 Forbidden and set an error message. Now test a URL that contains a script query to see if the content rule works as expected by returning the 403 error message. An example test URL could be as follows: https://test.domain.com/testscript.php?value=x<script>alert("XSS Attack!")</script> |
Workaround: | |
Notes: |
Content Rules Guide: https://support.kemptechnologies.com/hc/en-us/articles/7170469507341-Content-Rules Regex101: |