Products

Solutions

Resources

Search for API Security Tests

/

/

Sensitive files exposed due to SSRF

Sensitive files exposed 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 popular sensitive file paths. The application responded with 2XX success code and also gave out details of these files.

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 popular sensitive file paths. The application responded with 2XX success code and also gave out details of these files. 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 popular sensitive file paths. The application responded with 2XX success code and also gave out details of these files. 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 might compromise sensitive data such as passwords, source-code, confidential files etc.

Successful exploitation might compromise sensitive data such as passwords, source-code, confidential files etc.

How this template works

APIs Selection

The API selection filters in this template are used to identify potential SSRF vulnerabilities by checking if the request payload or query parameters contain URLs. It uses the "contains_either" keyword to match URLs that contain "http" in either the request payload or query parameters.

Execute request

The execute section of the template specifies the actions to be performed on the identified URLs. In this case, it modifies the query and body parameters by replacing them with the file paths specified in the "filePaths" word list.

Validation

The validation section defines the criteria for determining if the SSRF vulnerability has been successfully exploited. It checks if the response code is between 200 and 300 (indicating a successful request) and if the response payload contains any of the specified keywords such as "daemon", "Linux", "Ubuntu", or "/proc/self/cmdline". If these conditions are met, it suggests that sensitive files have been exposed due to SSRF.

Frequently asked questions

What is the purpose of the "FETCH_SENSITIVE_FILES" array in this test

How does the test determine if the endpoint is vulnerable to SSRF

What is the impact of successfully exploiting the SSRF vulnerability

What are some common concepts in application development that can increase the risk of SSRF attacks

Why are modern technologies like cloud providers, Kubernetes, and Docker more susceptible to SSRF attacks

Can the SSRF risk be completely eliminated? What factors should be considered when choosing a protection mechanism

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.