Skip to main content
kmak
Staff
Staff
July 15, 2025

Technical Tip: How to simulate a sample of a SSRF attack and using the Protected Hostname feature in FortiWeb to block the request

  • July 15, 2025
  • 0 replies
  • 193 views
Description This article describes the example of an SSRF attack and using the Protected Hostname feature in FortiWeb to block the request.
Scope FortiWeb.
Solution

One example of an SSRF attack can be simulated using the Burp Suite Community software.

 

  1. To simulate the attack, open the Burp Suite Community software. In the Proxy tab, turn on the Intercept option and open the browser. Browse the domain website so that the HTTP request will be intercepted by Burp Suite.

 

kmak_0-1752558195033.jpeg

 

  1. Right-click the request and select the option to Send to Repeater.

 

kmak_1-1752558195042.jpeg

 

  1. The request will now appear in the Repeater tab.

 

kmak_2-1752558195046.jpeg

 

  1. Change the request URL from '/' to some random hostname, which is just for testing purposes. Send the request to the website protected by FortiWeb but without the Protected Hostname policy. The request will be accepted with an HTTP return code'200'.

 

kmak_3-1752558195053.jpeg

 

kmak_4-1752558195061.jpeg

 

  1. Create the Protected Hostname Policy and enable the protection in the Server Policy. In FortiWeb, navigate to the Protected Hostname and create a new policy. The policy default action will be 'Deny'.

 

kmak_5-1752558195063.jpeg

 

  1. Create the accepting host list and enable the option based on the requirement.

 

kmak_6-1752558195065.jpeg

 

  1. After creating the Protected Hostnames policy, navigate to the respective Server Policy and enable the Protected Hostnames policy.

 

kmak_7-1752558195069.jpeg

 

  1. Resend the same SSRF attack request from the Burp Suite Community software now. The return code is now '500', which it should be the FortiWeb alert_deny return code.

 

kmak_8-1752558195078.jpeg

 

  1. Check on the FortiWeb Attack Logs page, and there will be an attack event triggered by the Protected Hostname policy whereby the request violated the rule.

 

kmak_9-1752558195088.jpeg

 

Related document:

Defining your protected/allowed HTTP “Host:” header names