SSRF Vulnerable Lab – Sample Codes Which Are Vulnerable SSRF attack

SSRF Vulnerable Lab -Practice SSRF attack xploitlab

One of critical vulnerabilities on website is Server-Side Request Forgery (SSRF), because with SSRF attacker can abuse functionality on the server to read or also update internal resources. The attacker can supply or a modify a URL which the code running on the server will read or submit data to. If you are a system administrator you need to know how to protect your server from this vulnerability.

Server-Side Request Forgery (SSRF) vulnerable Lab

This repository contain PHP codes which are vulnerable to Server-Side Request Forgery (SSRF) attack. This repository is help you to practice and learn about SSRF vulnerabilities.

I would like to say Thank You to @albinowax, AKReddy, Vivek Sir (For being great personalities who always supported me), Andrew Sir – @vanderaj (for his encouraging words) and those researchers who contirubuted in DNS rebinding attack based research.

Vulnerable codes are meant to demonstrate SSRF for below mentioned 5 scenarios:

1. Application code fetch and disply the content of the specified file

In programming language, there are functions which can fetch the content of locally saved file. These functions may be capable of fetching the content from remote URLs as well local files (file_get_contents in PHP).

This functionality can be abused if application is not prepending any string to the user supplied data to fetch the content from a file i.e application is not prepeding and directory name or path to the user supplied data.

In this case, application data fetching function process the schemes like “http://” or “file://”. When user will specify the remote URL in place of file name like “http://localhost“, data fetching function extract the data from the specified URL.

If application is prepending any data string (for example any directory name) to user data, in that case “http://” or “file://” scheme won’t work and SSRF vulnerability exploitation is not possible.

Guide to Exploitation of Scenario 1

2. Application provide interface to connect to Remote Host

Web application has interface allow an user to specify the any IP with any port. Here application may have functionality like, it try to connect to service like “MySQL”, “LDAP” etc.

Application expect user to specify the remote server hostname/IP, username and password in input fields. Application try to connect to the remote server over specified port. Here, application try to communicate to remote service listening on specific port. When vulnerable code has functionality to connect to server like MySQL and user specified the SMB port, vulnerable application will try to communicate to SMB servie using MySQL server service packets. Now, port is open, but services are not able to communicate due to difference in way of communication.

This behaviour can be exploited to perform internal network scanning not just to enumerate IPs but Ports as well on those live IPs.

Guide to Exploitation of Scenario 2

3. Application has File Download Functionality

In this case, an attacker can exploit this functionality to perform IP scanning inside the network where application server is hosted. The function which performs the task of downloding file from server, can download file not just from local server but also from SMB path as well. This is something which can help an attacker to figureout the windows based machines in the network.

Web application hosted on Windows OS will process the SMB path as well if file download functionality is processing user input without prepending any data.

Guide to Exploitation of Scenario 3

4. Bypassing IP blacklisting using DNS Based Spoofing

The script has funcionality which allow user to fetch data from remote URL. User need to specify the remote URL with any IP or domain name.

The script perform check if user has specified the input as “localhost”, “Internal IPs” or “Reserved IPs”. If domain/IP spcified by user is blacklisted, script will not fetch the content and stop processing.

Guide to Exploitation of Scenario 4

5. Bypassing IP blacklisting using DNS Rebinding Technique

Application has implemented black listing of not just internal and private range IPs but also rsolve the user supplied domain to its IP and again perform check if resolved is black listed or not.

In this case, DNS based spoofing trick will also not work to access the content hosted on internal/Reserved IP. Application code perform domain resolution to its IP and again perform black listed IP check for the resolved IP.

Guide to Exploitation of Scenario 5

You May Also Like

Leave a Reply

Your email address will not be published.

six + nine =