Products

Solutions

Resources

Search for API Security Tests

/

/

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

Sensitive localhost details exposed via replacing URI param redirecting to 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 make-127-0-0-1-rr.1u.ms/admin which redirects to localhost/admin.

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 make-127-0-0-1-rr.1u.ms/admin which redirects to localhost/admin. 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 make-127-0-0-1-rr.1u.ms/admin which redirects to localhost/admin. 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 template uses API selection filters to specify the criteria for selecting the APIs to be tested. In this case, the filters include checking the response code to be between 200 and 204, and checking if the request payload or query parameter contains the string "http".

Execute request

The template uses the execute section to define the actions to be performed during the execution phase. It specifies a single request to be made, where the query parameter and body parameter of the request are modified to replace the URL with "http://make-127-0-0-1-rr.1u.ms/admin".

Validation

The template uses the validation section to define the expected validation criteria for the response. It checks that the response code is between 200 and 299, and that the response payload contains the string "admin".

Frequently asked questions

What is the purpose of the SSRF_ON_LOCALHOST_DNS_PINNING test

How does modern application development contribute to the prevalence and severity of SSRF attacks

What are the potential impacts of a successful SSRF_ON_LOCALHOST_DNS_PINNING attack

What is the category and severity level of the SSRF_ON_LOCALHOST_DNS_PINNING vulnerability

What are the specific API selection filters used in the SSRF_ON_LOCALHOST_DNS_PINNING test

What modifications are made to the request in the execute phase of the SSRF_ON_LOCALHOST_DNS_PINNING test

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.