Unofficial documentation for the great tool Param Miner by James 'albinowax' Kettle.
I've used Param Miner for quite a long time but what many of it's checkboxes do remained a mystery for me. This repo aims to shine some light on purpose and use cases for some non obvious parameters of Param Miner. Information gathered here origins mostly from reading the source code.
| Parameter name | Description |
|---|---|
| Add 'fcbz' cachebuster | If checked: Param Miner adds fcbz=1 URL parameter to every request in order to avoid cache hits. |
| learn observed words | If checked: Param Miner extracts words from responses and saves them to current session's parameter wordlist. |
| only report unique params | ? |
| use basic wordlist | If checked: use headers and params wordlists from Param Miner's repo. |
| use custom wordlist | Self explanatory. |
| bruteforce | ??? but used only at this line |
| dynamic keyload | ??? This is the hard one - in order to understand it first need to understand how Param Miner works internally. Mostly related to ParamGuesser.addNewKeys function. |
| max one per host+status | ??? |
| enable auto-mine | If checked Param Miner will execute launchScan on every response processed at Proxy tab. Think of it like making Param Miner press Guess * buttons on every in-scope request for you. Also without it all other auto-* checkboxes won't take an effect. |
| auto-mine cookies | ? |
| auto-nest params | ??? This is the tough one, need further investigation. First it finds the most frequently occuring prefix and then uses it here. |
| try cache poison | ? |
| try -_ bypass | If checked: for every HTTP header with at least one dash Param Miner will replace dashes - with underscores _ and add resulting header to wordlist. Here is good explanation of why this works. |
| rotation interval | ??? |
| force bucketsize | ? |
| max param length | Determines maximum length for params parsed from response. Params with greater length truncated to this limit but not ignored! Note: it doesn't affect params supplied by any of wordlists. Also when determining a bucket size max param length is used as length of dummy parameters in trial payloads. |
| Add dynamic cachebuster | ??? |
| skip boring words | If checked: skip headers from boring_headers wordlist. |
| response | If checked: get words from HTTP response, normalize them and add to current session's parameter wordlist. |
| use bonus wordlist | If checked: use wordlists from Param Miner's repo. Normally used to include functions and words wordlists however if use basic wordlist isn't checked it will also add headers or params according to parameter type. |
| custom wordlist path | Path to user supplied wordlist of parameters. Note: it'll take an effect only when use custom wordlist is checked. |
| skip uncacheable | If checked: skips cookie and header params if no-cache string found in response. Perhaps it's useful if you're looking for cache poisoning attacks and you want to skip responses that won't be cached anyways. |
| max one per host | Related to rate-limiting. Perhaps don't allows to run more than 1 attack against a given host at a time. |
| scan identified params | If checked: run Burp Scanner on identified parameters. |
| auto-mine headers | ? |
| auto-mine params | ? |
| fuzz detect | If checked: appends <a`'"${{\ to input values to try and detect better-hidden params. |
| try method flip | If checked: for every non-GET request will use Burp's toggleRequestMethod which can be used to toggle a request's method between GET and POST. Parameters are relocated between the URL query string and message body as required, and the Content-Length header is created or removed as applicable. Finally results in this branch getting executed which tries to identify new parameters by making non-GET requests as GET requests. |
| thread pool size | ? |
| rotation increment | ??? |
| max bucketsize | Maximum number of parameters probed in one request. Note that for JSON parameters maximum bucketsize is 256. |
If you've found a mistake or just want to add something please fill free to create an Issue or even a Pull Request!