Sensitive AWS details exposed via replacing url param with encoded url 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 metadata endpoint provided by AWS in enclosed alphanumerics. 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 template uses API selection filters to specify the criteria for selecting the APIs to be tested. In this case, the filters are based on the response code, where the code should be greater than or equal to 200 and less than 205. Additionally, the filters check for the presence of certain keywords in the request payload or query parameters.
Execute request
The template specifies a single request to be executed. It modifies the query and body parameters by replacing the URL key with an encoded URL. This modification is done to simulate a Server Side Request Forgery (SSRF) attack. The encoded URL points to a metadata endpoint provided by AWS.
Validation
After executing the request, the template validates the response. It checks that the response code is between 200 and 300, indicating a successful request. It also checks that the response payload contains either "ami-id" or "ami-launch-index" or "ami-manifest-path" or "block-device-mapping" or "instance-action". If these conditions are met, it suggests that sensitive AWS information has been exposed, indicating a successful exploitation of the SSRF vulnerability.
Frequently asked questions
What is Server Side Request Forgery (SSRF) and how does it pose a risk to applications
How does the SSRF vulnerability in this test occur
What are some modern concepts in application development that make SSRF more common and dangerous
How does the impact of successful exploitation of this vulnerability affect AWS
What are the recommended protection mechanisms to mitigate SSRF risks
What are some references for further understanding and prevention of SSRF vulnerabilities
"The text editor in Akto is absolutely remarkable. Its user-friendly YAML format strikes the perfect balance between simplicity and power. With intuitive features like 'API selection filter', 'Execute', Validate' creating test rules becomes incredibly easy. Akto's test editor is a game-changer, enabling seamless creation of highly personalized and effective tests that could meet the needs of any modern day organization. "
Security team,
Rippling
Explore other tests
Sensitive files exposed due to SSRF
Port scanning with 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 file 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
