Sensitive AWS details exposed via replacing file param due to SSRF
The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing file parameter with sensitive file path. The application responded with 2XX success code and also gave out sensitive AWS information in response.
Server Side Request Forgery (SSRF)
How this template works
APIs Selection
The API selection filters in this template specify the conditions that the API request must meet in order to be selected for execution. In this case, the filters check for a response code between 200 and 204 (inclusive) and also look for the presence of a "file" parameter either in the request payload or query parameters.
Execute request
The execute section of the template defines the type of request to be executed (in this case, a single request) and provides the necessary modifications to the query parameter and body parameter. In this example, the "file_key" parameter is modified to have the value "///etc/passwd".
Validation
The validation section specifies the conditions that the response must meet in order to be considered valid. It checks for a response code between 200 and 299 (inclusive) and also uses a regular expression to validate the response payload, ensuring that it matches the pattern "root:.*:0:0:".
Frequently asked questions
Explore other tests
Sensitive files exposed due to SSRF
Port scanning with SSRF
Sensitive AWS details exposed via replacing url param with encoded url due to SSRF
Sensitive AWS details exposed due to SSRF
Sensitive AWS details exposed via replacing CSV param due to SSRF
Sensitive AWS details exposed via replacing image param due to SSRF
Sensitive localhost details exposed via replacing URI param with localhost/admin due to SSRF
Sensitive localhost details exposed via replacing URI param redirecting to localhost/admin due to SSRF
Sensitive localhost details exposed via replacing URI param to encoded localhost/admin due to SSRF
Sensitive AWS details exposed via replace PDF param due to SSRF
Sensitive AWS details exposed via replacing XML param due to SSRF