X-forwarder header does not work when vulnerability profile action changed to block ip

Poojadesai — Thu, 27 Apr 2023 10:21:48 GMT

ISSUE REPORTED: unable to block x-forwarder ip when the action is set to block ip in the vulnerability profile
------------------------------------------------------------------------------------------------------------------------

Discussion,observation, Troubleshooting:
------------------------------------------------------------------------------------------
++++ We have users accessing joomla website from wan and your proxy server is placed in dmz and application server is placed in lan

++++Traffic flow:

wan-------->dmz-------->lan

++++ we have 3 rules RULE 1. wan to dmz (Indian cx)

Rule 2. dmz to wan (Indian cx) url filtering profile (x forwarder enabled)+vulnerability profile(action= deny)

RULE 3. dmz to wan (non Indian cx with exceptions) url filtering profile (x forwarder enabled)+vulnerability profile(action= deny)------------want to change action to block-ip

In RULE 2 we would like action to be deny as we are not facing any threat attack from this traffic

In RULE 3 we want to block certain source IP's based on vulnerability signature therefore we want to set the vulnerability profile action as (Block -IP) based on X forwarder IP(Gives actual source IP). But currently when we change action to Block-IP we are able to block Proxy Ip and not the actual source IP. IN X-forwarder column we are getting right source IP but we are not able to block it.

When we set action as deny we are able to deny the source IP without issue but our requirement is to block the actual source IP and put it in blacklist. Right now when we use action=block ip it is blacklisting proxy ip.

In addition I am attaching few screenshots of security policy configured and also the screenshot of traffic logs when the action is set to block ip and ip that is sent to black list.

Re: X-forwarder header does not work when vulnerability profile action changed to block ip

delliott_6784 — Thu, 27 Apr 2023 12:07:52 GMT

Would it be possible to assign a user-id statically to the IP address you wish to block and use that user/IP mapping in the security policy to block the user and IP?

topic X-forwarder header does not work when vulnerability profile action changed to block ip in Next-Generation Firewall Discussions

X-forwarder header does not work when vulnerability profile action changed to block ip

Re: X-forwarder header does not work when vulnerability profile action changed to block ip