![]() ![]() ![]() Let's say that you want to connect a client that sends data to port 1234 to a remote server that is listening on port 5678. You can use this functionality to use Burp as a quick and simple port changer. For a practical example see Proxying Hipchat Part 2: So You Think You Can Use Burp?. First identify the endpoints and then add them to SSL Pass Through. This will cause the application to malfunction. Burp will MitM the non-HTTP connections and may silently drop or modify packets. This frequently happens with thick clients that use a mix of HTTP and non-HTTP protocols to talk to different endpoints. You add the endpoints to SSL Pass Through and see if the problem is with Burp. Suppose you are trying to proxy something but it doesn't work. Burp will not MitM anything added to this section and just act like a non-terminating TLS proxy. This is an underrated functionality of Burp ( Proxy > Options > SSL Pass Through). Match and replace rules 1.4 SSL Pass Through ![]() For example if the server responds to the login with true/false, I make a match/replace rule to modify the bad login response to true and bypass login (this will only work if the server does not care that your login was not successful). Another way is to automatically change something in the response to bypass client-side controls without patching the binary. I usually use it to change the User-Agent (see the default rules or add your own User-Agent). Meaning that you can replace something in the request or response with something of your choice. You can do match/replace under Proxy > Options > Match and Replace. You can also add your own rules and it supports regex to match the content and headers. There is a pre-defined rule to only intercept requests in scope. Go to Proxy > Options and see the rules Intercept Client/Server Requests. using the IE proxy settings) but only want to intercept traffic for some specific endpoints. This is extremely useful when you have redirected a lot of traffic to Burp (e.g. Intercepting responses 1.2 Intercepting Request/Responses Rulesīurp supports rules for intercepting requests/responses. Be sure to remove the checkbox on the first rule, otherwise binary payloads may not be intercepted. Enable it at Proxy > Options > Intercept responses based. Sometimes you want to intercept the response for manual modification. You can configure most of these settings in Proxy > Options. Interceptionīurp supports request/response interception and modification. If you have any favorite tips or usecases and want them included with credit please let me know, as usual feedback is always welcome. Please note that these series of posts are not targeted towards web application testing so I have skipped some functionalities. When I started this, I did not think I have so much stuff to write about Burp. Most settings have not changed since I started working with Burp (v1.5). This part one I talk about Interception and Proxy listeners which are configured via Proxy > Options.Īt the time of writing the current version of Burp Pro is 1.6.39 and most items should apply to the current Burp Free version ( 1.6.32). ![]() One purpose is to share it with the world and not be the other guy from Wham! (:D) and the other is to have it in an accessible place (similar to the cheat sheet in the menu). I am going to document a bunch of Burp tips and tricks that have helped me during my work. If the application is using HTTP methods then Burp is your best friend. I usually use it during mobile and thick client tests. Bonus tip: Running Burp with a Set Amount of Memoryīurp is not just used for web application testing. 1.6 Disable Intercept at Startup and Miscellaneous.1.2 Intercepting Request/Responses Rules. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |