Some web applications implement IP-based protection rules that restrict users from accessing particular pages of an application like an admin page if their IP addresses are not in the allowed list. These rules are used as an access control mechanism.
It relies on having a proxy between the client and the server for forwarding requests. The proxy forwards the clientโs IP to the server; if it is allowed or whitelisted, the server will respond with the requested page; otherwise, it will block the request.
The proxy does that by adding an X-Forwarded-For header that contains the clientโs IP address to the request before sending it to the application. Then, the application checks the X-Forwarded-For header to determine whether the IP address of the client is in the allowed list.
๐ The X-Forwarded header accepts two directives a client IP and proxy IP. It is possible to include multiple proxy IPs to send the requests; the traffic will bounce through the IPs successively before reaching the server.
**
๐ Syntax: X-Forwarded-For: ,,,
**
The attackers can take advantage of this and test the restriction rules by spoofing a different IP that they know is allowed by the application, like localhost address 127.0.0.1. Tricking the application into thinking the requests come from a trusted source, even though the original requests are coming from a different blocked IP.
Since it is a pain to modify requests manually in attempts to bypass these WAF restriction rules, Burp can help automatically insert the required headers into each request sent to the application.๐
There are 2 methods to achieve our goal through Burp Suite, either through the match and replace rules, which actually what I use all the time before discovering the Bypass WAF extension.
I was unaware of the extension before working on the Control machine on HTB, and I came across it when researching for better ways to automate forwarding requests.
Even though I liked using the extension, I am going to include both methods for reference ๐ .
Letโs begin !!
Method #1: Match/Replace Rules
1- Navigate to the Proxy tab and click on Options. Scroll down to the Match and Replace section and click Add.
2- Specify the details needed for the matched Rule. We start first with specifying the Type of Rule; in our case, it is a Request Header since we want Burp to insert the modified header into all client requests.
Next, in the Match field, leave it blank to match all requests.
In the Replace field, we will enter the **X-Forwarded-For **header with the IP address we want to send requests from.
๐ Adding a comment is optional but helpful if you are using multiple rules at the time.
When done, click Ok to save the rule.
3- Check the Enabled box to enable the new Rule.
Now, we have the Rule configured, letโs test it out. Turn Foxy Proxy On or add the proxy setting to the browser, and refresh the page.
If we intercept the request with Proxy, we see Burp added the X-forwarded header in all the sent requests.
**
Method #2: Bypass WAF Extension
**
The extension can be installed and configured to send X-forwarded headers automatically each time you navigate to the application.
1- Go to the Extender tab and click on the Burp BApp Store. Scroll down to the right pane and click on the **Install **Button.
When the extension is installed, it will be added in the Extensions tab, and a new tab will be added in Burp Suite Tabs.
๐ก You can remove an extension by going to the Extensions Tab and click on Remove.
2- Next, we need to add a session handling rule to make Burp perform the required actions when making the HTTP requests.
Go to Project options and click on Sessions, then click Add.
Insert the name of the Rule in the Rule Description and the action needed in Rule Actions. In our case, we want to Invoke Burp Extension that will allow us to use the Bypass WAF extension.
4- In the Scope tab, check the Proxy box to enable it.
For the URL scope, we can either choose to Include all URLs or Use a Targeted scope โUser suite scope [defined in Target tab].
5- Next, we configure the extension, click on the Bypass WAF, add the IP address in the Header field and click on Set Configuration to enable the bypass configuration.
6- Refresh the page, and test the extension.
Great!! The extension works. The downside is when intercepting the requests, I donโt see the X-Forwarded-For headers are added like with the Match & Replace rule.
With a bit of research, I found that I can install the Flow extension to monitor the requests I send to the proxy and see how the Bypass WAF injects the x-forwarded header.
7- Go back to the BApp Store and install Flow.
In the extension tab, make sure the Flow extension is added under the Bypass WAF extension. (๐ order matters when monitoring requests).
8- Now refresh the page and go to the Flow tab. We can see the headers Bypass WAF injects to the requests we send to the server.
Thatโs all for today, Thanks reading.
Sincerely,
Dmitry Sorokin,
403 Gone
REChain, Inc
Katya AI, Systems
Katya, Inc
Katya Systems, LLC
REChain Network Solutions
Top comments (0)