Most Read This Week
Security & Cloud Computing
Metasploit Nessus Bridge on Ubuntu
Nessus is a vulnerability scanner program
By: David Dodd
Jul. 1, 2011 10:00 AM
Nessus is a vulnerability scanner program; it is free for personal use using the nessus for home. They also have a nessus for business which requires a fee. I will be discussing the nessus for home use and using it with the popular metasploit framework. Acquire the latest release of nessus homefeed Nessus-4.4.1-ubuntu1010_i386.deb and register for the activation code. Follow the instructions listed in the document ion for installing with Ubuntu and start to configure. Nessus daemon cant be started until nessus has been registered and the plugin download has occurred.
Open up web browser to https://localhost:8834, login and complete a policy for your scans. I would create a number of policies based on the different systems that you will be scanning. If your scanning a windows environment then having the plugin for Linux and BSD are pointless. Also make sure that you have safe checks enabled, select a port scanner to use, select credentials, select plugins (remember not to enable ones that will bounce the box), and select preferences. When finished you should have a number of different policies that will be numbered 1 – however many you have and you can give them names for example for scanning windows environment you can label them as windows. Now you can logout of nessus and close the web browser.
Now open up a terminal and browse to where metasploit is installed and run an update.
$ cd /opt/framework-3.6.0/msf3
Before we start the msfconsole lets get our database in proper order. Now I have used sqlite3 in the past and even did a tutorial on my website using sqlite3 http://pbnetworks.net/?cmd=bbs&id=35 which worked fine but sometimes it may not work and give error warning 'Note that sqlite is not supported due to numerous issues. It may work, but don't count on it.' Postgres is the recommended database for Metasploit. So lets install the postgres database and libraries.
$ sudo apt-get install postgresql-8.4
You will need to become the system postgres user
$ sudo -s
Now you will need to create a database user:
$ createuser <user account name> -P
$ createdb –owner=<user account name> msf_database
Now we can start up metasploit:
:/opt/framework-3.6.0/msf3$ sudo ./msfconsole
Enter in the following commands:
msf> db_driver postgresql
Now before, when using sqlite3, creating and connecting to the database was easy. I would start up metasploit and issue the following commands:
msf> db_driver sqlite3
To verify if the database was connected I would issue the following command:
If everything looked good I would have no errors and I could use the db_nmap command. But sometimes I would encounter errors and it would crash. Using postgres is more reliable than sqlite3 but is still useful as I will describe later. Finally go ahead and enable the database on startup by issuing the following commands:
$ cat > ~/.msf3/msfconsole.rc
Now the next time you fire up metasploit your database will automatically be up and you will be connected to it. Just make sure that you have postgres running, I run postgres manually before I start metasploit. (see Figure 1)
Figure 1 Notice that postgresql loads when first starting the msfconsole
$ sudo /etc/init.d/postgresql-8.4 start
Now just change directory over to /opt/framework-3.6.0/msf3 and start the msfconsole. Now that we have postgres as the database for metasploit lets start using nessus from within metasploit. Open up a second terminal and make sure nessus is running if not load the daemon. Now from the msfconsole load nessus (see Figure 2)
msf > load nessus
Now let see what kind of commands the Nessus Bridge for Metasploit 1.1 has given us, type nessus_help (see Figure 3)
Figure 3 nessus_help
msf > nessus_help
The commands are divided up into different sections labeled Generic, Reports, Scan, Plugin, User, and Policy commands. Before we can run a scan we need to connect to the nessus server by using the nessus_connect command:
This should connect and authenticate you. From here you can run the scans, review the results, and load the scan results into the database and use autopwn feature. Or you can view the results and find a vulnerability with a system you scanned and throw a single exploit and get a meterpreter shell. Depending on the environment you may want to review the results of your nessus output and find the appropriate exploit to use instead of generating the noise of running autopwn. Now lets start our scan by issuing nessus_scan_new command as follows nessus_scan_new <policy id> (this was set in your nessus policy settings) <scan name> (generic) <target> (ip address)
msf > nessus_scan_new 1 winXP_home 192.168.1.124
To check up on the status of our scan use the nessus scan status feature (see Figure 4)
msf > nessus_scan_status
When the scan has completed you can view the results using the following commands:
msf > nessus_report_list
We can view a list of hosts from the report with the following command:
msf > nessus_report_hosts UID
To view further information issue the following command:
msf > nessus_report_host_ports <ip address> UID (see Figure 5)
Figure 5 nessus_report_host_ports 192.168.1.124 UID
To see a list of hosts issue the db_host command. If you want to remove hosts from the db_hosts file then issue the db_del_host command (see Figure 6)
Now with the scan complete and the host listed in the db_hosts file you can run the autopwn tool or find an exploit that will work against the box. More on this in another article next month.
Now lets take a look at using nmap within the metasploit framework.
To use the nmap command from within the metasploit framework use the 'db_nmap' command to run nmap scans against targets and have the scan results stored in the database. When running on Back|Track I can issue many different nmap commands such as db_nmap -sS -sV -T 3 -P0 -O <ip address> -D RND --packet-trace. Which show the results: -sS TCP SYN stealth scan, -sV version scan, -T 3 normal scan, -O find the operating system, -D RND use a decoy and generate a random, non-reserved IP address, and finally --packet-trace will trace packets and data sent and received. I like to use the packet-trace feature on large scans because if it fails you can see it. Now this is great feature to use while in the msf console but I cant do this when using Unbuntu and connected to the postgres database as the postgres user. Why? Because I get an error saying that only the root user has the ability to use this nmap option (see Figure 7). I can use 'db_nmap -v -sV 192.168.15.0/24 --packet-trace' and the scan runs and produces an output. I have view the results with the following commands (see Figure 8).
msf > db_hosts
Figure 6 db_del_host command
Figure 7 nmap error with postgres
Now if I want to issue complex nmap scans I can exit out of the msf prompt, exit out of postgres, stop the database and login with sudo and use the sqlite3 database. The same command that the OS didn't allow me to use now can be used with no problem (see Figure 9)
msf > db_nmap -sS -sV -T 4 -P0 -O 192.168.15.0/24 -D RND --packet-trace
Look at the difference in results we now have after viewing information in the db_hosts and db_services -c port,state commands. Compare difference between Figure 10 and Figure 8 below.
Figure 8 db_nmap using postgres database
Figure 9 db_nmap using sqlite3
Figure 10 nmap results using sqlite3
On the 'Net
Let pbnetworks get your pen test on target
Visit us and learn how http://pbnetworks.net
How secure is your network?
Subscribe to the World's Most Powerful Newsletters
Today's Top Reads