Products

Solutions

Resources

Search for API Security Tests

/

/

Sensitive localhost details exposed via replacing URI param with localhost/admin due to SSRF

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)

"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. Modern concepts in application development make SSRF more common and more dangerous. More common - the following concepts encourage developers to access an external resource based on user input: Webhooks, file fetching from URLs, custom SSO, and URL previews. More dangerous - Modern technologies like cloud providers, Kubernetes, and Docker expose management and control channels over HTTP on predictable, well-known paths. Those channels are an easy target for an SSRF attack. It is also more challenging to limit outbound traffic from your application, because of the connected nature of modern applications. The SSRF risk can not always be completely eliminated. While choosing a protection mechanism, it is important to consider the business risks and needs."

"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. Modern concepts in application development make SSRF more common and more dangerous. More common - the following concepts encourage developers to access an external resource based on user input: Webhooks, file fetching from URLs, custom SSO, and URL previews. More dangerous - Modern technologies like cloud providers, Kubernetes, and Docker expose management and control channels over HTTP on predictable, well-known paths. Those channels are an easy target for an SSRF attack. It is also more challenging to limit outbound traffic from your application, because of the connected nature of modern applications. The SSRF risk can not always be completely eliminated. While choosing a protection mechanism, it is important to consider the business risks and needs."

Impact of the vulnerability

Impact of the vulnerability

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

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!

Loved by security teams!

Product Hunt Badge

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

Loom Company logo

Security team,

Loom

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

Loom Company logo

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

Rippling Company logo

Security team,

Rippling

Suggest API security tests

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.

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.