What You Need To Know About Server Side Request Forgery (SSRF)

Last updated: October 3, 2017 | 4,136 views

SSRF or Server Side Request Forgery is an attack vector that has been around for a long time, but do you actually know what it is?

Server Side Request Forgery (SSRF) refers to an attack where in an attacker is able to send a crafted request from a vulnerable web application. SSRF is usually used to target internal systems behind firewalls that are normally inaccessible to an attacker from the external network.

What You Need To Know About SSRF - Server Side Request Forgery

Typically Server Side Request Forgery (SSRF) occurs when a web application is making a request, where an attacker has full or partial control of the request that is being sent. A common example is when an attacker can control all or part of the URL to which the web application makes a request to some third-party service.

There are various things you can use SSRF for such as:

Scanning other machines within the private network of the vulnerable server that aren’t externally accessible
Performing Remote File Inclusion (RFI) attacks
Bypassing firewalls and use the vulnerable server to carry out malicious attacks
Retrieving server files (including /etc/passwd etc)

This is example code in PHP that is vulnerable to SSRF:

<?php

/**
* Check if the 'url' GET variable is set
* Example - http://localhost/?url=http://testphp.vulnweb.com/images/logo.gif
*/
if (isset($_GET['url'])){
$url = $_GET['url'];

/**
* Send a request vulnerable to SSRF since
* no validation is being done on $url
* before sending the request
*/
$image = fopen($url, 'rb');

/**
* Send the correct response headers
*/
header("Content-Type: image/png");

/**
* Dump the contents of the image
*/
fpassthru($image);
}