I frequently use tools like ffuf to illustrate fuzzing to my students.
Using the following command, for instance:
bash
┌──(kali㉿localhost)-[~]└─$ffuf -w wordlist.txt -u http://mydomaintarget.org/FUZZ
Files like backup.sql, graphql.txt, config.json, and other possibly sensitive files may be discovered in this way.
To confirm their presence, we employ:
┌──(kali㉿localhost)-[~]└─$curl -I http://mydomaintarget.org/backup.sql on mydomaintarget.org
The server replies with an HTTP 200 status if the file is present. When we try to download the file, though: backup.sql using
bash
┌──(kali㉿localhost)-[~]└─$curl -o http://mydomaintarget.org/backup.sql on mydomaintarget.org
The output is a JavaScript obfuscated code rather than the anticipated content.
Are there any explainations to such behavior?
Using the following command, for instance:
bash
┌──(kali㉿localhost)-[~]└─$ffuf -w wordlist.txt -u http://mydomaintarget.org/FUZZ
Files like backup.sql, graphql.txt, config.json, and other possibly sensitive files may be discovered in this way.
To confirm their presence, we employ:
┌──(kali㉿localhost)-[~]└─$curl -I http://mydomaintarget.org/backup.sql on mydomaintarget.org
The server replies with an HTTP 200 status if the file is present. When we try to download the file, though: backup.sql using
bash
┌──(kali㉿localhost)-[~]└─$curl -o http://mydomaintarget.org/backup.sql on mydomaintarget.org
The output is a JavaScript obfuscated code rather than the anticipated content.
Are there any explainations to such behavior?
