-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Closed
Description
Setting either the -x or --replay-proxy options to some incorrect value results in ffuf running and ignoring the proxy value. This lead to me accidentally putting http:/127.0.0.1:8080 as the replay proxy and then spending the next 20 minutes questioning the fabric of reality.
Some validation of these flags and an error when they're invalid would be a good addition.
$ ~/go/bin/ffuf -x "asdfasdf asf" --replay-proxy "asdfasdf qwer" -w test -u http://127.0.0.1:8000/FUZZ -mc all
/'___\ /'___\ /'___\
/\ \__/ /\ \__/ __ __ /\ \__/
\ \ ,__\\ \ ,__\/\ \/\ \ \ \ ,__\
\ \ \_/ \ \ \_/\ \ \_\ \ \ \ \_/
\ \_\ \ \_\ \ \____/ \ \_\
\/_/ \/_/ \/___/ \/_/
v1.5.0-dev
________________________________________________
:: Method : GET
:: URL : http://127.0.0.1:8000/FUZZ
:: Wordlist : FUZZ: test
:: Follow redirects : false
:: Calibration : false
:: Proxy : asdfasdf asf
:: ReplayProxy : asdfasdf qwer
:: Timeout : 10
:: Threads : 40
:: Matcher : Response status: all
________________________________________________
:: Progress: [4/4] :: Job [1/1] :: 0 req/sec :: Duration: [0:00:00] :: Errors: 4 ::
bugbaba and esp0xdeadbeef
Metadata
Metadata
Assignees
Labels
No labels