Anti-CSRF Token From Referer
The extension works by registering a new session handling rule called "Anti-CSRF token from referer". This handler inspects all the requests and searches for the anti-CSRF token parameter (in GET, POST, JSON and multipart requests) determine$
Once this parameter is found, a GET request is issued to the referer of the original request. In this request, all the headers are copied from the original request (e.g Cookie, Authorization...).
This response is then parsed and the substring between the start and the end markers configured in the tab is extracted as the anti-CSRF token.
Finally, the anti-CSRF token is replaced in the original request.
- Create a new session handling rule (Invoke a Burp extension > Anti-CSRF token from referer)
- Define session scope
- Configure parameters in Anti-CSRF token from referer tab
For further information, consult the documentation on https://github.com/CompassSecurity/anti-csrf-token-from-referer/blob/master/README.md
|Last updated||28 February 2020|
You can install BApps directly within Burp, via the BApp Store feature in the Burp Extender tool. You can also download them from here, for offline installation into Burp.
|You can view the source code for this BApp by visiting our GitHub page.|
|Follow @BApp_Store on Twitter to receive notifications of all BApp releases and updates.|
Please note that extensions are written by third party users of Burp, and PortSwigger Web Security makes no warranty about their quality or usefulness for any particular purpose.