Server-Side Request Forgery (SSRF)
What is Server-Side Request Forgery (SSRF)?
Server-Side Request Forgery (SSRF)A web vulnerability that allows an attacker to coerce a server into making HTTP or other network requests on their behalf, often against internal systems.
Server-Side Request Forgery (SSRF) arises when a server fetches a remote resource using a URL that the user influences, without validating the destination. The attacker borrows the server's network position to reach services a firewall would otherwise block — cloud metadata endpoints, admin consoles, internal APIs, databases — to read data, scan ports, or trigger further exploitation. SSRF entered the OWASP Top 10 in 2021 as category A10, reflecting how common and damaging it became in cloud deployments.
Two incidents define the risk. In the 2019 Capital One breach, Paige Thompson exploited an SSRF in a misconfigured web application firewall to query the AWS Instance Metadata Service (http://169.254.169.254/), retrieve the EC2 role's temporary IAM credentials, and exfiltrate data on roughly 100 million customers — the event that drove AWS to ship IMDSv2, which requires a session token obtained by a PUT request and so resists the classic GET-based SSRF. In early 2021, ProxyLogon (CVE-2021-26855) was a pre-authentication SSRF in Microsoft Exchange that, chained with CVE-2021-27065, gave unauthenticated attackers remote code execution; it was mass-exploited and added to CISA's KEV catalog. Defences: allowlist outbound hosts rather than blocklisting, resolve and re-check the IP to reject link-local (169.254.0.0/16), private (RFC 1918), and loopback ranges after DNS resolution to stop DNS-rebinding, disable unused schemes (file://, gopher://), require authentication on internal services, and enforce IMDSv2 or its equivalent.
flowchart TD
A[Attacker submits crafted URL<br/>e.g. image/webhook/PDF import] --> B[Vulnerable server fetches URL<br/>no destination validation]
B --> C{Target of the request}
C -->|169.254.169.254| D[Cloud metadata service]
D --> E[Leak temporary IAM credentials]
C -->|10.0.0.0/8 internal| F[Admin panel / database]
F --> G[Read data, port scan, pivot]
E --> H[Cloud account takeover / exfiltration]
B -. defended by .-> X[Allowlist + block private/link-local IPs<br/>post-resolution + IMDSv2]● Examples
- 01
An attacker abuses an image-import feature to fetch http://169.254.169.254/ and steal cloud instance credentials.
- 02
An SSRF in a webhook endpoint is used to scan internal databases that are otherwise unreachable from the internet.
● Frequently asked questions
What is Server-Side Request Forgery (SSRF)?
A web vulnerability that allows an attacker to coerce a server into making HTTP or other network requests on their behalf, often against internal systems. It belongs to the Attacks & Threats category of cybersecurity.
What does Server-Side Request Forgery (SSRF) mean?
A web vulnerability that allows an attacker to coerce a server into making HTTP or other network requests on their behalf, often against internal systems.
How do you defend against Server-Side Request Forgery (SSRF)?
Defences for Server-Side Request Forgery (SSRF) typically combine technical controls and operational practices, as detailed in the full definition above.
What are other names for Server-Side Request Forgery (SSRF)?
Common alternative names include: SSRF.