Blind SSRF in URL Validator

Introduction :

Hello Amazing Hackers! I’m Yash Kandekar, and In this blog I’ll be sharing an Interesting bug which led me to my first paid Blind SSRF :)

I will try my best to make this Blog as Fun and Interesting as possible! So let’s get started !

The Story starts from me Testing on a program to find any “Valid” bugs, but unfortunately couldn’t find any as the Program was already tested Heavily by many good hackers (The Usual story). But this program was relying on APIs and as you know, APIs aren’t always 100% properly configured!

Let’s call our Target as as I cannot disclose the Real Target’s name. is our Target

URL Validator:

The Application had a Feature to Post anything on your Feed. Here you can Introduce any browse-able Links as well. Think of Twitter , where you can paste a link in your post, and twitter makes an Interaction with that link to Validate it ? Same situation was here but with HTTP interaction!

The API will make a request to that link (to validate it) :

This is an Intended Feature and not a Bug.

The Problem:

We couldn’t just use localhost or or right in the url section and hope for a positive reply from :(

I used a Lot of Payloads, different encodings of for nearly 1–2 hours, but no Positive response from server. Also, using payloads like (for port scanning) was not working .

The Solution :D

After Roaming around the Infosec internet for a relevant resource, I found this recent Gem Report from SirLeeroyJenkins

This Included an Attacker server which will be hosting a script (PHP for example), which will redirect the Incoming requests to another destination. We can setup our own server using Ngrok and PHP.

Actual Blind SSRF :

This is how we will reproduce the Issue :

Prepare a PHP script “redir.php” which will redirect the incoming requests

  1. Setup Ngrok and PHP on your side :

Note that both commands are executed at same path.

a) $ ngrok http 80 #This will start our ngrok server

b) $ PHP -S #This will let the php script execute, once requests are received.

2.Navigate to and add our ngrok URL with script path:

3. Forward the request, notice the port we included in our script, it is ‘443’. This will return Noticeably faster response. As will first visit and then redirect to itself, since 443 was open port it results in faster response.

requesting a Valid port

4. Now just change the port from 443 to something potentially inactive like ‘54321’. Once we send the request, it will return a Delayed response, because will be searching for this port and will try to make a connection (but fails, miserably).

I tried to increase the impact, like switching the protocol to gopher, but was protected with various filters.

And that’s how Folks, I managed to mark my first paid Blind SSRF from a heavily tested application.

There is no Secret sauce, as the wise zseano says, stick to one program, you will eventually find something interesting !

Till then, Stay safe and do Hunting Baazi !

Thank you for Reading till here .

Just a lazy boi trying to figure out his life.