The Debug Options

The BrowserBruter provides two options to help pentester get insights of working of BrowserBruter to better understand the fuzzing process or troubleshoot some issue.

These options are

Debug Option:
  --verbose             Use this switch to enable HTTP request/response output being printed on console and STDLOG file.
  --debug               Use this switch to print the Stack Trace messages in case of the error! and keep the logs in log file.

Note: Whenever any of these switch is used, a log file is generated at logs/BrowserBruterSTDOUT.txt.

Getting HTTP traffic on runtime using --verbose

The --verbose switch can be used to print the HTTP traffic on console and logs/BrowserBruterSTDOUT.txt file on runtime. This can be helpful to get insights on going attack.

python3 BrowserBruter.py --elements username,password --payloads fuzz.txt --target http://localhost/login1.php --button btn-default --attack 1 --fill username,password --headless --no-css --verbose

This console output is logged in logs/BrowserBruterSTDOUT.txt file too for later inspections.

This flag can be combined with --interactive (or manually going into interactive mode, learn here) to run see HTTP traffic of each fuzz attempt one by one in interval manner.

Getting Exceptions using --debug flag

In case of exceptions, the generic error messages are printed on the console. However, if you want the stack traces of the errors, you can get it using --debug flag.

Note: Even you don't use the --debug flag, the stack traces and errors are always being logged in logs/Error.txt

Hope on to the next section to learn about options that alter the report generations.