Course contentsShow
← Security
Lesson 888 of 3,05218. Web Security - CSRF and Request ForgeryFree lesson

Blind SSRF Detection and Exploitation

Identifying SSRF when no response is returned using DNS exfiltration, timing attacks, and out-of-band techniques.

Blind SSRF Detection and Exploitation

You'll learn how to identify and exploit Server-Side Request Forgery vulnerabilities when the application doesn't return the HTTP response to you.

The Invisible Attack Surface

In traditional SSRF, you send a malicious URL and the server returns the fetched content directly to your browser. Blind SSRF is trickier—the server makes the request you specify, but you never see the response. It's like asking someone to check if a door is locked, but they never tell you the answer. You need creative ways to infer what happened.

Detection Techniques

DNS Exfiltration: The most reliable method. You provide a URL pointing to a domain you control (like http://your-unique-id.attacker.com). If you see a DNS lookup in your server logs, you've confirmed the vulnerability exists—the target made an outbound request.

Timing Attacks: Request a URL with an intentional delay (http://internal-service:9999 that times out versus http://localhost:80 that responds quickly). Measure how long the application takes to respond. Significant timing differences reveal which services exist and respond.

Out-of-Band Techniques: Use services like Burp Collaborator or Interactsh that monitor for:

  • DNS queries
  • HTTP requests
  • SMTP connections

When the vulnerable server contacts your monitoring endpoint, you have proof—and potentially exfiltrated data encoded in the subdomain or request path.

Why This Matters

Even without seeing responses, blind SSRF lets attackers:

  • Confirm internal services exist
  • Port scan internal networks
  • Trigger actions (like password resets sent to attacker-controlled servers)
  • Bypass IP-based access controls

Key Takeaway: Blind SSRF requires external infrastructure you control to detect the vulnerability through DNS logs, timing analysis, or out-of-band callbacks—absence of visible responses doesn't mean absence of impact.