[Openvas-discuss] Why is OpenVAS is missing obvious open ports?
whit at transpect.com
Fri Aug 3 15:43:38 CEST 2012
On Fri, Aug 03, 2012 at 09:30:51AM -0400, Whit Blauvelt wrote:
> On Fri, Aug 03, 2012 at 03:01:15PM +0200, Henri Doreau wrote:
> > do you have nmap installed on the scanner box? Although nmap is not a
> > hard requirement for OpenVAS, the scanner is able to leverage it and
> > this can dramatically improve accuracy of the network exploration
> > phase.
> Thanks for the suggestion.
> The Atom process resulted in nmap 5.51 being installed. Does OpenVAS require
> special configuration to use it?
By comparison nmap has no trouble seeing the open ports in the remote range
when run from that same VM. Here's just one IP per "nmap -T4 -F":
Host is up (0.025s latency).
Not shown: 90 closed ports
PORT STATE SERVICE
22/tcp open ssh
53/tcp open domain
80/tcp open http
111/tcp filtered rpcbind
113/tcp filtered auth
135/tcp filtered msrpc
139/tcp filtered netbios-ssn
443/tcp open https
445/tcp filtered microsoft-ds
3306/tcp filtered mysql
So if OpenVAS is trying to leverage nmap results, that's failing.
More information about the Openvas-discuss