This is a collection of extensions to Burp Suite that I have written.

This is an evolution of the original getAllParams extension for Burp. Not only does it find more potential parameters for you to investigate, but it also finds potential links to try these parameters on. This is to be used instead of the original getAllParams extension if you want to make use of the additional link functionality. The full Help documentation can be found [here] (https://github.com/xnl-h4ck3r/burp-extensions/blob/main/GAP%20Help.md) or from the Help icon on the GAP tab.

Good luck and good hunting! If you really love the tool (or any others), or they helped you find an awesome bounty, consider BUYING ME A COFFEE! ☕ (I could use the caffeine!)

This is a python extension that runs in Portswigger's Burp Suite and parses an already crawled sitemap to build a custom parameter list. It also adds common parameter names that could be useful in the final list used for fuzzing.

Although it has a different function, the code was based on the why-cewler.py extension by Ianmaster53 (https://gist.github.com/lanmaster53/a0d3523279f3d1efdfe6d9dfc4da0d4a) just as a base template.

Usage:

1. Point Burp Suite to the Jython .jar file in Extender > Options > Python Environment.
2. Install this extension manually in the Extender > Extensions tab.
3. Change any options on the "Get All Params" tab.
4. Right-click on any element in the Target tab's hierarchical sitemap.
5. Select the Extensions > Get All Params context menu item.
6. Go to the "Get All Params" tab to see the results.

If the option to save output to a file is selected then a file of all parameters will be created in the users home directory (or Documents for Windows) with the name {TARGET}_getAllParams.txt The extension Output tab will show a combined string of all parameters and a test value (default of of XNLV? - where ? is a unique number) This string can be used in requests and then Burp history searched for any reflection of XNLV

REQUEST PARAMETERS: The following types of parameters with in the Burp IParameter interface can be returned (depending on selected options):

• PARAM_URL (0) - Used to indicate a parameter within the URL query string.
• PARAM_BODY (1) - Used to indicate a parameter within the message body.
• PARAM_COOKIE (2) - Used to indicate an HTTP cookie.
• PARAM_XML (3) - Used to indicate an item of data within an XML structure.
• PARAM_XML_ATTR (4) - Used to indicate the value of a tag attribute within an XML structure.
• PARAM_MULTIPART_ATTR (5) - Used to indicate the value of a parameter attribute within a multi-part message body (such as the name of an uploaded file).
• PARAM_JSON (6) - Used to indicate an item of data within a JSON structure.

RESPONSE PARAMETERS:

• JSON parameters (Thanks to contribution by @_pichik)
• XML parameters (Thanks to contribution by @_pichik)
• Words from URL paths, if you are using this to generate a wordlist (Thanks to contribution by @_pichik)
• Name and Id attribute from HTML Input fields
• Javascript variables and constants in ALL types of responses (JS vars could be in the html, script and even JSON response within a .js.map file)
• Meta tag Name attribute