The Biggest Agentic AI Security Summit

The Secure, Governed AI Future.

October 27, 2026 | Virtual

The Biggest Agentic AI Security Summit

The Secure, Governed AI Future.

October 27, 2026 | Virtual

The Biggest Agentic AI Security Summit

The Secure, Governed AI Future.

October 27, 2026 | Virtual

/

/

Sensitive AWS details exposed via replace PDF param due to SSRF

Sensitive AWS details exposed via replace PDF param due to SSRF

The endpoint appears to be vulnerable to Server Side Request Forgery attack. The original request was replayed by replacing PDF 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)

How this template works

APIs Selection

The template uses API selection filters to specify the criteria for selecting the API requests to be executed. 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 ".pdf" value.

Execute request

The template specifies a single request to be executed. It modifies the query parameter and body parameter named "pdf_key" by replacing it with a URL that redirects to an AWS IMDS endpoint. This is done to simulate a Server Side Request Forgery (SSRF) attack.

Validation

The template includes validation criteria for 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, it indicates a successful exploitation of the SSRF vulnerability.

Frequently asked questions

What is the purpose of this test

How does SSRF vulnerability occur

What are some common scenarios that make SSRF more prevalent

Why is SSRF considered more dangerous in modern technologies

Why is it challenging to limit outbound traffic from modern applications

How should protection mechanisms against SSRF be chosen

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