In short
A SSRF (Server-Side Request Forgery) vulnerability allows an attacker to force a server to send requests to an address of their choice, including internal services that are inaccessible from the Internet. It is particularly serious in the cloud, where it can grant access to metadata services and infrastructure credentials. While it was a separate category in the 2021 OWASP Top 10, it is now grouped under “Weak Access Control” (A01) in the 2025 edition.
An example
An application allows users to import an image from a URL. Instead of an image, the attacker provides the address of an internal service, such as a database administration interface or the cloud provider’s metadata service. The server, located on the internal network, retrieves the resource and returns the response to the attacker.
What an attacker can gain
- Temporary cloud credentials via the metadata service, followed by access to the infrastructure.
- Internal network mapping and access to unprotected interfaces.
- Reading local files based on accepted protocols.
How to Protect Against It
- Allow only necessary destinations (whitelist), and resolve and then verify the final IP address.
- Block internal address ranges and metadata addresses, including after redirection.
- Enable the cloud provider’s protections (e.g., IMDSv2 on AWS).
- Isolate components that need to retrieve external resources.
Frequently asked questions
Why is SSRF critical in the cloud?
This is because cloud providers’ metadata services, which are accessible from the server, can reveal identifiers that grant access to the infrastructure itself.
Sources
Find out where an attacker would get in.
Our AI agents actually attack your scope, fully automated, and hand you the proof of every vulnerability.
