Sensitive localhost details exposed via replacing URI param with 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. The application responded with 2XX success code and also gave out admin-related details.

Server Side Request Forgery (SSRF)

Impact of the vulnerability

Successful exploitation can lead to access control bypass, sensitive data leak, or even compromise the application.

How this template works

APIs Selection

The API selection filters in this template specify the conditions that the response code or request payload must meet in order for the vulnerability to be detected. In this case, the filters check if the response code is between 200 and 204 (inclusive) and if the request payload contains the string "http" in either the URL key or query parameter.

Execute request

The execute section of the template defines the actions to be performed during the execution phase. It specifies a single request to be made, where the query parameter and body parameter with the key "url_key" are modified to replace the value with "http://localhost/admin".

Validation

The validation section sets the criteria for validating the response received from the executed request. It checks if the response code is between 200 and 299 (inclusive) and if the response payload contains the string "admin". If both conditions are met, the vulnerability is considered to be present.

Frequently asked questions

What is the purpose of the SSRF_ON_LOCALHOST array in this test

How does the test identify potential SSRF vulnerabilities

What modifications does the test make to the requests

How does the test validate the success of the SSRF attack

What are the potential impacts of a successful SSRF attack

How does the test handle false positives or false negatives

Loved by security teams!

"We are absolutely thrilled with the testing feature of Akto. We have used it on our graphQL endpoints and it performs flawlessly identifying common API security issues. It's truly a game-changer and we highly recommend Akto to anyone looking to effortlessly secure their API endpoints. With a user-friendly interface, it's the perfect solution for anyone looking to embrace custom rules with context to reduce false positives."

Security team,

Loom

Security team,

Loom

Security team,

Loom

"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

Security team,

Rippling

Security team,

Rippling

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 file param due to SSRF

Sensitive AWS details exposed via replacing image param 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

Learn more:

Content

7 min read

Server-Side Request Forgery: Proactive SSRF Prevention Tactics for Developers

Content

10 min read

What's changed in OWASP API Security Top 10 2023 Release Candidate from 2019?

Suggest API security tests

We're actively building the test library. Suggest a test! If we like your suggestion, you will see it in the library in few days.