How this template works
The API selection filters in this template are used to filter the requests based on the response code. In this case, the filter is set to only select requests with a response code equal to 302 (redirect).
The execute section of the template specifies the type of execution (single) and the requests to be executed. In this case, the requests include adding various headers with the value "evil.com" to test for open redirect vulnerability. The follow_redirect parameter is set to false to prevent automatic redirection.
The validation section defines the criteria for validating the response. It checks if the response code is equal to 302 and if the response headers contain the key "location" with a value that contains either "evil.com". This ensures that the response indicates a redirect to a potentially malicious website.
Frequently asked questions
What is the purpose of injecting 'evil.com' into the host headers in this test
How does an open redirect vulnerability pose a risk to the application and its users
What is the impact of the OPEN_REDIRECT_HOST_HEADER_INJECTION subcategory
What are the selection filters used in this test
What headers are being added to the request in this test
What validation criteria are used to determine the success of the test