Metasploit Basics, Part 5: Using Metasploit for Reconnaissance

Welcome back, my rookie hackers!
As you know, reconnaissance is a crucial part of the hacker/pentester's job. Without good reconnaissance, it is likely that all your work and effort will go for naught. As Metasploit has evolved from strictly an exploitation framework to a multi-faceted penetration testing tool, it has added additional capabilities including reconnaissance. No longer do you need to carry separate tools for reconnaissance and then exploitation. Metasploit can do it all.
Now, with thepostgresql database attached to Metasploit, we can save our results from port scanning and vulnerability scanning into the database and then use those results in the next phase of the penetration test.
Step #1 Fire Up Metasploit
The first step, of course, is to fire up Kali and start the msfconsole.
kali > msf
Step # 2 nmap and db_nmap
Usually, before starting a hack, we want to gather as much info on the target as possible. Let's begin by finding out what ports are open. Metasploit enables us to runnmapright from the msf prompt. Let's try scanning a systems on our local area network with a TCP scan (-sT) looking for open ports between 1 and 1000 (-p1-1000).
msf >  nmap -sT 192.168.1810/24 -p1-1000
As you can see above, nmap was able to scan all the machines on our internal network and return the results of the open ports.
As I demonstrated inMetasploit Basic, Part 4, you can also use thedb-nmapcommand to scan and save the results into Metasploit's postgresql attached database. In that way, you can use those results in the exploitation stage later.
msf > db_nmap 192.168.181.0/24
Step #3 Scanning Modules
Metasploit has a multitude of scanning modules built in. If we open another terminal, we can navigate to Metasploit'sauxiliary modulesand list all thescannermodules.
cd /usr/share /metasploit-framework/modules/auxiliary
kali > ls -l
Note in the screenshot above, the numerous directories containing modules for all sorts of auxiliary purposes. Let's navigate to the scanner directory and look inside.
kali > cd scanner
kali > ls -l
As you can see below, there are hundreds of scanner modules each inside a directory of a specific target type.
Let's go to the scada directory and look inside there.
As you can see there are 11 scada scanner modules.
Step #4 Conducting a SCADA Scan
Let's try using one of those scada scanner modules to conduct a scan on a SCADA system (for more on SCADA Hacking, see mySCADA serieshere).
msf > use auxiliary/scanner/scada/modbusclient
We need to set the RHOST, the NUMBER of coils to read and READ_COIL parameters.
As you can see in the screenshots above, we used this scada scanner to read the coils (the coils are ON/OFF switches inside the SCADA facility) on a remote SCADA system. This would be the first step before exploiting this system.
Step #5 MS SQL Login Scan
Among the numerous scans within Metasploit is one that can enumerate logins on Microsoft's flagship database server, SQL Server.
We can use this module by typing;
msf > use auxiliary/admin/mssql/mssql_enum_sql_logins
After loading the module, we learn more about this scanner by typinginfo.
msf > info
As you can see in the description, this module can be used to fuzz available SQL Server logins providing us with logins that can then be brute forced with one of many different password cracking tools.
Once we provide it an RHOST, it begins scanning for available logins on the database server.
msf > set RHOST 192.168.181.129
msf > exploit
As you can see above, this scanner was able to find the login "sa" account or the sysadmin of this SQL Server installation!
Conclusion
Reconnaissance is a crucial phase of the hacking/penetration testing process. Metasploit has added hundreds of reconnaissance modules, so that we may complete most of our reconnaissance right from Metasploit. Here, I have demonstrated just a few reconnaissance modules in Metasploit, but there are literally hundreds more so take some time to explore the many recon modules in Metasploit and it will likely save you hundreds of hours in your hack/pentest.


from hackers-arise full article here