Home

/

Test

/

Sensitive AWS details exposed via replacing XML param due to SSRF

Sensitive AWS details exposed via replacing XML param due to SSRF

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing XML upload parameter with url that redirects to AWS IMDS endpoint. The application responded with 2XX success code and also gave out sensitive AWS information in response.

Server Side Request Forgery (SSRF)

"The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing XML upload parameter with url that redirects to AWS IMDS endpoint. The application responded with 2XX success code and also gave out sensitive AWS information in response. Server-Side Request Forgery (SSRF) flaws occur whenever an API is fetching a remote resource without validating the user-supplied URL. It allows an attacker to coerce the application to send a crafted request to an unexpected destination, even when protected by a firewall or a VPN.\n "Modern concepts in application development make SSRF more common and more dangerous.\n" "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.\n" "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.\n" "It is also more challenging to limit outbound traffic from your application, because of the connected nature of modern applications.\n" + "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 XML upload parameter with url that redirects to AWS IMDS endpoint. The application responded with 2XX success code and also gave out sensitive AWS information in response. Server-Side Request Forgery (SSRF) flaws occur whenever an API is fetching a remote resource without validating the user-supplied URL. It allows an attacker to coerce the application to send a crafted request to an unexpected destination, even when protected by a firewall or a VPN.\n "Modern concepts in application development make SSRF more common and more dangerous.\n" "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.\n" "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.\n" "It is also more challenging to limit outbound traffic from your application, because of the connected nature of modern applications.\n" + "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 AWS information which attacker can use to get unauthorized access to AWS.

Successful exploitation might compromise sensitive AWS information which attacker can use to get unauthorized access to AWS.

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 a ".xml" extension.

Execute request

The template uses a single execution type, which means it will execute a single request. The request is modified by replacing the "xml_key" query parameter and body parameter with a specific URL. This modification is done using the "modify_query_param" and "modify_body_param" actions.

Validation

After executing the request, the template validates the response. It checks if the response code is between 200 and 299, indicating a successful request. It also checks if the response payload contains any of the specified sensitive AWS information, such as "ami-id" or "block-device-mapping". If the validation criteria are met, the test is considered successful.

Frequently asked questions

What is the purpose of this test

What is the purpose of this test

What is the purpose of this test

How does SSRF vulnerability occur

How does SSRF vulnerability occur

How does SSRF vulnerability occur

What are some common scenarios that make SSRF more prevalent

What are some common scenarios that make SSRF more prevalent

What are some common scenarios that make SSRF more prevalent

Why is SSRF considered more dangerous in modern technologies

Why is SSRF considered more dangerous in modern technologies

Why is SSRF considered more dangerous in modern technologies

Why is it challenging to limit outbound traffic from modern applications

Why is it challenging to limit outbound traffic from modern applications

Why is it challenging to limit outbound traffic from modern applications

Can SSRF risk be completely eliminated

Can SSRF risk be completely eliminated

Can SSRF risk be completely eliminated

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

"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

"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

"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

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

Learn more:

Prevent-SSRF
Prevent-SSRF
Prevent-SSRF

Content

7 min read

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

top-10-owasp-apisecurity-2019
top-10-owasp-apisecurity-2019
top-10-owasp-apisecurity-2019

Content

10 min read

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

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.