Blind SSRF Exploitation
Introduction: When Responses Stay Silent
In the previous lessons, you exploited SSRF vulnerabilities where the server fetched a URL and returned its content directly to you. This made exploitation straightforward — you could see AWS metadata, internal API responses, and other sensitive data immediately. However, many applications make server-side requests without ever showing you the response. They might test a webhook URL, verify a configuration, or trigger a notification, but the response content stays on the server.
This scenario is called Blind SSRF, and while it seems safer because you cannot read the response, attackers have developed clever side-channel techniques to exploit these vulnerabilities. By performing timing analysis, triggering DNS lookups, or observing error messages, attackers can map internal networks, confirm vulnerabilities, and even exfiltrate data. In this lesson, you will learn how to exploit blind SSRF through timing analysis and DNS exfiltration, then build defenses that prevent these attacks using webhook allowlists and timeout controls.
Anatomy of a Blind SSRF Vulnerability
Let's examine a typical blind SSRF vulnerability in a webhook configuration endpoint. Many applications allow users to register webhook URLs that the server will call when certain events occur. To ensure the webhook is reachable, the application tests it by making a request during configuration. However, the application only tells you whether the test succeeded or failed — it never shows you the response content.
Here's what this vulnerable endpoint looks like:
The endpoint accepts a webhookUrl from the request body and immediately makes a POST request to that URL with a test payload. The timeout setting of 5000 milliseconds means the request will wait up to 5 seconds for a response. Notice what happens after the request: the endpoint only returns success: true or success: false based on whether the request succeeded. The actual response data from webhookUrl is completely ignored.
This appears safer than the URL import vulnerability you exploited earlier because there is no way to read the response. If you point webhookUrl at the AWS metadata service, you will know the request succeeded, but you will not see the instance credentials or any other sensitive data. However, this "blindness" does not eliminate the risk — it just changes the attack techniques you need to use.
Why is this still dangerous? Even without seeing response content, attackers can accomplish several malicious goals. They can scan internal networks to map out services and open ports, confirm the existence of internal systems, trigger side effects on internal APIs (like password resets or account deletions), and exfiltrate data through DNS queries. The fact that you cannot see responses makes exploitation more challenging, but far from impossible.
