CyberKit

Server-Side Request Forgery

Also called SSRF.

Coercing a server into making attacker-chosen network requests.

What it is

A vulnerability that lets an attacker make a server send requests to destinations of the attacker's choosing, including internal services and metadata endpoints. The server's trusted position is abused to reach otherwise unreachable targets.

Why it matters

SSRF is a major cloud-era risk because it can reach internal APIs and instance metadata to harvest credentials. It is frequently the pivot that turns an external bug into internal access.

In practice

An image-fetch feature is pointed at an internal metadata service, returning temporary cloud credentials to the attacker.

What to look for

  • Requests to cloud metadata addresses such as 169.254.169.254.
  • URL parameters that the server fetches.
  • Outbound requests from app servers to internal hosts.

Common mistake

Blocking only 127.0.0.1. Redirects, DNS tricks and other encodings get around simple filters.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Burp Suite Commercial

    An intercepting proxy for testing web apps by hand and with its scanner.

  • ZAP Open source

    An open source web app scanner and proxy, often run in CI pipelines.

  • Cloudflare WAF Commercial

    Blocks common web attacks at the edge while the code gets fixed.

Read next

Sources