Module 12: Locating Public Exploits
Last updated
Last updated
Read code before executing it if you didn't write it. Don't be stupid.
Useful columns on the Exploit-DB outside the obvious.
D: Download the exploit.
A: Download the application files for investigation/review.
V: Specifies if the exploit is verified.
Google Dorking, pretty straight-forward.
Some exploit frameworks:
Metasploit
Core Impact
Canvas
Browser Exploitation Framework (BeEF)
Local copy of the exploit database is stored in /usr/share/exploitdb/
. This directory is split into exploits and shellcodes. It contains CSV files for each of the directories with information on all files in the two subdirectories.
Copy an exploit to your current directory: searchsploit -m path/to/exploit.py
or searchsploit -m edb-id
Nmap's Scripting Engine directory can be found at /usr/share/nmap/scripts/
. Information on the scripts can be found by running nmap --script-help=script-name.nse
.
Nothin' specific to this section, note-wise. This was a walkthrough of using what was covered in the module to exploit a target.
Automatic URL encoding for those pesky web RCEs:
curl http://target/path/to/backdoor.php --data-urlencode "cmd=which nc"