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.
- Risk Scoring
Score a vulnerability with CVSS v3.1, or an incident across five dimensions, and see the reasoning behind each number.
- Map and Score
Map real procedures to ATT&CK techniques, then pick the CVSS v3.1 metrics for real vulnerabilities.
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
- Path Traversal: Using crafted paths to reach files outside the intended directory.
- Broken Access Control: Failure to enforce what authenticated users are allowed to do.
- Command Injection: Injecting attacker commands into a shell call the app builds.