Home page logo

metasploit logo Metasploit mailing list archives

Re: db_services bug?
From: Tod Beardsley <todb () planb-security net>
Date: Tue, 21 Jun 2011 10:19:07 -0500

Seems to work for me under normal circumstances. Need to run
msfconsole as root of course to get UDP scan. This was on r12995.

msf auxiliary(ssh_login) > db_nmap -T4 -ff -sU -p 5353
[*] Nmap: Starting Nmap 5.51SVN ( http://nmap.org ) at 2011-06-21 10:17 CDT
[*] Nmap: Nmap scan report for dbsrv (
[*] Nmap: Host is up (0.00053s latency).
[*] Nmap: 5353/udp open  zeroconf
[*] Nmap: MAC Address: 00:0C:29:A5:9E:F3 (VMware)
[*] Nmap: Nmap done: 1 IP address (1 host up) scanned in 0.31 seconds
msf auxiliary(ssh_login) > db_services


host            port  proto  name      state  info
----            ----  -----  ----      -----  ----  5353  udp    zeroconf  open

msf auxiliary(ssh_login) >

On Tue, Jun 21, 2011 at 9:05 AM, Scott McClellan <Scott.McClellan () tn gov> wrote:
I'm running the 3.8.0-dev version of Metasploit (rev 12980), updated
yesterday.  My database had no hosts in it.  I ran db_nmap -T4 -ff -sU on my
target.  I then ran db_services, but the only value in the proto column was
tcp.  I know that my target has open UDP ports.  I'm using the Postgresql
database, with msfconsole.  I'm running Metasploit from within BackTrack 5.

Has anyone else seen this behavior?


  By Date           By Thread  

Current thread:
  • db_services bug? Scott McClellan (Jun 21)
    • Re: db_services bug? Tod Beardsley (Jun 21)
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]