Attacking a web app
ffuf
A fast web fuzzer: puts each wordlist entry where FUZZ is in the request and keeps the matches.
ffuf -u URL/FUZZ -w WORDLIST replaces the FUZZ marker with each line of the wordlist and sends the
request, the same path-discovery job as gobuster done a different way. You choose what counts as a hit: -mc 200
matches a status code, -fc 404 or -fs SIZE filters out the noise. Because FUZZ can sit anywhere, ffuf also
fuzzes query parameters, headers and host names, not just paths. -s prints only the matching values.
ffuf command usage
ffuf -u URL/FUZZ -w WORDLIST [-mc CODES] [-fc CODES] [-fs SIZES] [-e EXTENSIONS] [-s] [-t THREADS] [-o FILE] ffuf --help
Options
-
-u http://10.0.1.20/FUZZ - the URL, with FUZZ marking where each word is inserted
-
-w /usr/share/dirb/wordlists/common.txt - the wordlist whose lines replace FUZZ
-
-mc 200 - match (keep) only responses with these status codes
-
-fc 404 - filter out (hide) responses with these status codes
-
-fs 250 - filter out responses of these byte sizes: the way to drop a uniform 'not found' page
-
-e .php,.txt - also try each word with these extensions appended
-
-s - silent: print only the matching values, no banner or progress
-
-t 40 - how many requests to make at once
-
-o finds.json - also write the results to the file after it
ffuf examples
-
ffuf -u http://10.0.1.20/FUZZ -w /usr/share/dirb/wordlists/common.txt -mc 200 -s - Guesses paths on the target and prints only those that answer 200.
backup
-
ffuf -u 'http://10.0.1.20/search?q=FUZZ' -w /usr/share/dirb/wordlists/common.txt -fc 404 - Fuzzes a query parameter's value instead of a path.
Pitfalls
- Without a matcher or filter the default keeps several status codes; narrow it (
-mc 200) or the noise buries the find. - Like any guesser it finds only what the wordlist contains.