See-SURF

A Python based scanner to find potential SSRF parameters in a web application. See-SURF helps you detect potential SSRF parameters and validates the finding it by making a DNS/HTTP request back to your server. It can be added to your arsenal of recon while doing bug hunting/web security testing.

Tech/framework used

Built with

• Python3

Installation

git clone https://github.com/In3tinct/See-SURF.git
cd See-SURF/
pip3 install BeautifulSoup4
pip3 install requests

How to use?

Burp Sitemap (-b switch check below if you don't know what that is) & Connect back to your server ( -p switch )

Complete Command would look like this -
python3 see-surf.py -H https://www.google.com -c cookie_name1=value1 cookie_name2=value2 -b burp_file.xml -p http://72.72.72.72:8000
-H - Host name/Ip address
-c - Cookies seperated by space (Some websites use multiple cookies for session tracking
-b (Optional but recommended) - Spider the request using burp, export the file and give it to see-surf as input (check detailed features on how to do it)
-p (Optional but recommended) - Your own web server/burp collaborator, the script will try to connect back for validation of SSRF params

Features

1. Takes burp's sitemap as input and parses and parses the file with a strong regex matches any GET/POST URL parameters containing potentially vulnerable SSRF keywords like URL/website etc. Also, checks the parameter values for any URL or IP address passed. Examples GET request -
   google.com/url=https://yahoo.com
   google.com/q=https://yahoo.com
   FORMS -
   <input type="text" name="url" value="https://google.com" placeholder="https://msn.com">
   
   
2. Multi-threaded In-built crawler to run and gather as much data as possible to parse and identify potentially vulnerable SSRF parameters. by default it uses 10 threads.
   
   
3. Supply cookies for an authenticated scanning.
   python3 see-surf.py -H https://www.google.com -c cookie_name1=value1 cookie_name2=value2
   
   
4. By default, normal mode is On, with a verbose switch you would see the same vulnerable param in different endpoints. The same parameter may not be sanitized at all places. But verbose mode generates a lot of noise.
   python3 see-surf.py -H https://www.google.com -c cookie_name1=value1 cookie_name2=value2 -t 20 -v
   Example:
   https://google.com/path/1/urlToConnect=https://yahoo.com
   https://google.com/differentpath/urlToConnect=https://yahoo.com
   
   
5. Exploitation - Makes an external request to burp collaborator or any other http server with the vulnerable parameter to confirm the possibility of SSRF.
   
   

Version-2 Features

[-] -b switch Provide burp sitemap files for a better discovery of potential SSRF parameters. The script would first parse the burp file and try to identify potential params and then run the built in crawler on it

Browser the target with your burpsuite running at the background, make some GET/POST requests, the more the better. Then go to target, right click-> "Save selected Items" and save it. Provide to the script as follows.
python3 see-surf.py -H https://www.google.com -c cookie_name1=value1 cookie_name2=value2 -b burp_file.xml

)

[-] -p switch Fire up burpsuite collaborator and pass the host with -p parameter Or start a simple python http server and wait for the vulnerable param to execute your request. (Highly Recommended)
(This basically helps in exploiting GET requests, for POST you would need to try to exploit it manually)
Payload will get executed with the param at the end of the string so its easy to identify which one is vulnerable. For example: http://72.72.72.72:8000/vulnerableparam

python3 see-surf.py -H https://www.google.com -c cookie_name1=value1 cookie_name2=value2 -p http://72.72.72.72:8000

Contribute

• Report bugs.
• Suggestions for improvement.
• Suggestions for future extensions.

Future Extensions

• Include more places to look for potential params like Javascript files
• Finding potential params during redirection.
• Exploitation.
• Hidden parameters.

License

GNUV3 © [In3tinct]