36.1 FFUF: Fast Web Fuzzing
FFUF (Fuzz Faster U Fool) ek vegvaan web fuzzer aahe. Request madhe FUZZ he word theva – tool wordlist madhun pratyek shabd tyachyajagi takto aani response baghto. Gobuster sarkhe directory shodh, pan parameter ani virtual host fuzzing pan ekach tool madhe. Kali var:
sudo apt update && sudo apt install -y ffuf
ffuf -h # help – flags lakshat theva
Directory fuzzing (hidden paths shodhayche):
ffuf -u http://192.168.56.20/FUZZ \
-w /usr/share/wordlists/dirb/common.txt \
-mc 200,301,302,403
-u madhe URL, FUZZ jithe shabd basel. -w wordlist. -mc match status codes (200 found, 301/302 redirect, 403 forbidden-but-there).
Parameter fuzzing (konte query params accept hotaat):
ffuf -u "http://192.168.56.20/dvwa/vulnerabilities/sqli/?FUZZ=1" \
-w /usr/share/wordlists/dirb/common.txt \
-mc 200 -fs 0
Virtual host fuzzing (Host header badlun):
ffuf -u http://192.168.56.20 -H "Host: FUZZ.lab.local" \
-w /usr/share/seclists/Discovery/DNS/subdomains-top1million-5000.txt \
-fw 20
Useful filters: -fc 404 (filter out status), -fs 1234 (filter by response size – default page size ignore karayla), -fw 50 (filter by word count), -t 10 (threads), -rate 50 (requests per second – lab madhe pan soft raho).
Defence: WAF / rate-limit lava, unusual 404 floods log kara, backup files (.bak, .old) production var thevu naka, ani sensitive paths la authentication (प्रमाणीकरण) lavun theva. Samjla ka?
Ravindra Bagale's Tip
Not every row in FFUF's output is "interesting". Students use -mc all and drown in noise. First use -mc 200,301,403, then remove the default page size with -fs. Watch the Size column – where the size is different, that's a real find. Keep a rate limit (-rate) even in the lab – otherwise your DVWA will hang.
Ravindra Bagale's Tip – मराठी
FFUF च्या output मध्ये सगळ्या rows "interesting" नसतात. Students -mc all लावून noise मध्ये बुडतात. आधी -mc 200,301,403 आणि मग -fs ने default page size काढून टाका. Size column बघा – जिथे size वेगळी, तिथे खरा find आहे. Rate limit (-rate) lab मध्ये पण ठेवा – नाहीतर तुमचा DVWA hang होईल.
Ravindra Bagale's Tip – हिंदी
FFUF के output में सारी rows "interesting" नहीं होतीं. Students -mc all लगाकर noise में डूब जाते हैं. पहले -mc 200,301,403 और फिर -fs से default page size हटा दो. Size column देखो – जहाँ size अलग है, वहीं असली find है. Rate limit (-rate) lab में भी रखो – वरना आपका DVWA hang हो जाएगा.
Lab
Kali (192.168.56.10) varun DVWA (http://192.168.56.20/dvwa/) var FFUF directory fuzzing chalaa (common.txt, -mc 200,301,403). Tin interesting paths note kara. Mag aaplya reels app (Chapter 16) var same scan – kontehi .bak kiwa admin path disla tar remove kara.
Extended teaching notes
Why this lesson matters
Kali tools are dual-use. In this course every run ends with a defensive note: what config would have blocked or detected the activity on a system you own.
Rule
Host-only lab, written scope, no bridging onto real LANs.
Mini case study
Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.
Defender's worksheet (do this today)
- Write the lesson title, date and the exact lab target you are allowed to use.
- List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
- Run one safe check from the lesson on a lab system only. Paste the command and output.
- Write a two-sentence fix you would give a teammate.
- Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.
Indian workplace (sample data)
Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).
Global practice
Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.
Everyday analogy
Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.
Key terms
- Control: a safeguard (patch, config, process, detection).
- Finding: a weakness backed by evidence.
- Remediation: the fix plus how you verified it.
- Scope: systems you have written permission to touch.
- Least privilege: only the access the task needs.
- Defence in depth: several layers so one failure does not end the story.
Common mistakes
- Skipping written permission "just for a quick scan".
- Practising on hostel, office or public targets without authorisation.
- Collecting tool output without writing the fix.
- Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
- Publishing screenshots that contain secrets, cookies or internal hostnames.
Recap
- Evidence, fix, owner, date.
- Own lab only.
- Fix > spectacle.