Port scanning with SSRF

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing the URI parameter with some of the popular ports. The application responded with 2XX success code indicating that the port is open.

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 are used to filter requests based on specific criteria. In this case, the filters are checking if the request payload or query parameter contains the string "http". If the condition is met, the request will be selected for further processing.

Execute request

The execute section of the template specifies the actions to be performed on the selected requests. In this case, the template modifies the query parameter and body parameter of the selected requests by replacing the "url_key" with the values specified in the "filePaths" word list.

Validation

The validation section defines the criteria for validating the response of the executed requests. It checks if the response code is between 200 and 299 (indicating a successful response) and if the response payload matches any of the provided regular expressions. If the validation criteria are met, the request is considered successful.

Frequently asked questions

What is the purpose of this test

How does SSRF vulnerability occur

What are some modern concepts that make SSRF more common and dangerous

Why is it challenging to limit outbound traffic from modern applications

What are the potential impacts of successful exploitation of SSRF vulnerability

How can developers protect against SSRF attacks

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

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 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

Learn more:

Content

4 min read

Introducing AktoGPT to secure APIs

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.