Sensitive localhost details exposed via replacing URI param to encoded localhost/admin due to SSRF
The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing the URI parameter with localhost/admin in an encoded format. The application responded with 2XX success code and also gave out admin-related details.
Server Side Request Forgery (SSRF)
How this template works
The template uses API selection filters to specify the criteria for selecting the requests to be executed. In this case, the filters check for a response code between 200 and 204, and also check if the request payload or query parameter contains the string "http". If any of these conditions are met, the request will be selected for execution.
The template specifies a single request to be executed. It modifies the query parameter and body parameter by replacing the URL key with an encoded localhost/admin URL. This is done to simulate a Server Side Request Forgery attack. The modified request is then sent to the target endpoint.
After executing the request, the template validates the response received. It checks if the response code is between 200 and 299, indicating a successful request. It also checks if the response payload contains the string "admin". If both of these conditions are met, the validation is considered successful.
Frequently asked questions
What is the purpose of the SSRF_ON_LOCALHOST_ENCODED test in this array
How does modern application development contribute to the prevalence and severity of SSRF attacks
What are the potential impacts of successfully exploiting an SSRF vulnerability
What is the category and severity level assigned to this SSRF vulnerability
What are the specific API selection filters used in this test
How does the test modify the query and body parameters in the requests