
Server-side request forgery (SSRF) tricks your server into making HTTP requests on the attacker's behalf. Because the request comes from inside your network, it can reach systems the attacker cannot reach directly.
In cloud environments SSRF is especially dangerous: the cloud metadata service can hand out temporary credentials to whoever asks from inside the instance.
Features that fetch a URL, such as link previews, webhooks, PDF generators, image importers and "import from URL", take an address from the user. If the server does not restrict where it may connect, an attacker can point it at internal admin panels, databases, or the cloud metadata endpoint.
Blind SSRF gives no response back, but the attacker can still detect it through DNS lookups or timing.
Blind SSRF is when the server makes the attacker-controlled request but does not return the response. It can still be detected through DNS lookups, timing or out-of-band interactions.
Cloud instances can query a metadata service for temporary credentials. An SSRF that reaches it can hand an attacker access to the whole cloud account.
Try Vooki Pro free for 7 days
SSRF is behind some of the largest cloud breaches. Check your application for it today. The trial unlocks every feature for 7 days, and scanning runs on your own machine.
Related: Server-side template injection (SSTI) · IDOR and broken object-level authorization (BOLA)