Greenbone missing some open ports during discovery

Scanning / scan configuration
1

Hi all,

I’m seeing inconsistent port discovery results with Greenbone. When I cross-check with other tools, I find that Greenbone is missing several open ports (like 8080, 9200) that are definitely accessible and responsive.

I’m scanning all IANA ports in my configuration (e.g: 3001/TCP), and the standard ports are detected fine by Greenbone, but it seems to miss higher numbered or less common service ports. This is problematic since missed ports mean missed vulnerability tests.

Has anyone experienced similar issues with Greenbone’s port scanner being less comprehensive despite scanning the full IANA range? Are there specific scanner settings I should adjust to improve port detection coverage?

Thanks for any suggestions.

2

GVM (OpenVAS) runs an Nmap scan on the host and operates based on the results. Manually verify whether the ports are visible by running an Nmap scan from the OpenVAS machine.

Eero

3

Are you sure you used ALL TCP as Portlist ? Or just the IANA assinged ports.

You can define what ports needed to be scanned first …

4

That does not help, if he selected the wrong portlist :wink:

5

Also keep in mind that the GUI is not implemented for port scanning capabilities (e.g. to show all open TCP ports). For example the “Ports” tab in the reports GUI described below is only listing the ports for which at least one results matching the current filter has been found. AFAICT this is by design / the desired functionality.

6

This topic was automatically closed after 90 days. New replies are no longer allowed.