Sent from my iPhone
> On Jun 25, 2018, at 10:01 PM, Daryn Utesbayev <dutesba...@gmail.com> wrote: > > Hi, > We deployed OpenVas in our organization for monitoring vulnerabilities. After > that we checked many targets host to get reports of vulnerabilities. Further > OpenVAS scans produce reports displaying multiple services running but > without vulnerabilities results according to below. Are you doing authenticated scans? > > CPE: cpe:/a:openbsd:openssh:7.4 > Concluded from remote connection attempt with credentials: > Login: VulnScan > Password: VulnScan > </value><source><type>nvt</type><name>1.3.6.1.4.1.25623.1.0.10267</name><description>Service > detection > (1.3.6.1.4.1.25623.1.0.10267)</description></source><extra/></detail><detail><name>App</name><value>cpe:/a:openbsd:openssh:7.4</value><source><type>nvt</type><name>1.3.6.1.4.1.25623.1.0.10267</name><description>Service > detection > (1.3.6.1.4.1.25623.1.0.10267)</description></source><extra/></detail><detail><name>cpe:/a:openbsd:openssh:7.4</name><value>22222/tcp</value><source><type>nvt</type><name>1.3.6.1.4.1.25623.1.0.10267</name><description>Service > detection > > So why OpenVAS doesn't scan vulnerabilities? > > Environment is > VM Linux kali 4.16.0-kali2-686-pae #1 SMP Debian 4.16.12-1kali1 (2018-05-28) > i686 GNU/Linux with selinux disabled; > openvas-check-setup 2.3.7 > Test completeness and readiness of OpenVAS-9 > > Please report us any non-detected problems and > help us to improve this check routine: > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > > Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the > problem. > > Use the parameter --server to skip checks for client tools > like GSD and OpenVAS-CLI. > > Step 1: Checking OpenVAS Scanner ... > OK: OpenVAS Scanner is present in version 5.1.1. > OK: redis-server is present in version v=4.0.10. > OK: scanner (kb_location setting) is configured properly using the > redis-server socket: /var/run/redis-openvas/redis-server.sock > OK: redis-server is running and listening on socket: > /var/run/redis-openvas/redis-server.sock. > OK: redis-server configuration is OK and redis-server is running. > OK: NVT collection in /var/lib/openvas/plugins contains 45687 NVTs. > OK: Signature checking of NVTs is enabled in OpenVAS Scanner. > OK: The NVT cache in /var/cache/openvas contains 45687 files for > 45687 NVTs. > Step 2: Checking OpenVAS Manager ... > OK: OpenVAS Manager is present in version 7.0.2. > OK: OpenVAS Manager database found in /var/lib/openvas/mgr/tasks.db. > OK: Access rights for the OpenVAS Manager database are correct. > OK: sqlite3 found, extended checks of the OpenVAS Manager > installation enabled. > OK: OpenVAS Manager database is at revision 184. > OK: OpenVAS Manager expects database at revision 184. > OK: Database schema is up to date. > OK: OpenVAS Manager database contains information about 45683 NVTs. > OK: At least one user exists. > OK: OpenVAS SCAP database found in /var/lib/openvas/scap-data/scap.db. > OK: OpenVAS CERT database found in /var/lib/openvas/cert-data/cert.db. > OK: xsltproc found. > Step 3: Checking user configuration ... > WARNING: Your password policy is empty. > SUGGEST: Edit the /etc/openvas/pwpolicy.conf file to set a password > policy. > Step 4: Checking Greenbone Security Assistant (GSA) ... > OK: Greenbone Security Assistant is present in version 7.0.2. > OK: Your OpenVAS certificate infrastructure passed validation. > Step 5: Checking OpenVAS CLI ... > OK: OpenVAS CLI version 1.4.5. > Step 6: Checking Greenbone Security Desktop (GSD) ... > SKIP: Skipping check for Greenbone Security Desktop. > Step 7: Checking if OpenVAS services are up and running ... > OK: netstat found, extended checks of the OpenVAS services enabled. > OK: OpenVAS Scanner is running and listening on a Unix domain socket. > WARNING: OpenVAS Manager is running and listening only on the local > interface. > This means that you will not be able to access the OpenVAS Manager > from the > outside using GSD or OpenVAS CLI. > SUGGEST: Ensure that OpenVAS Manager listens on all interfaces unless > you want > a local service only. > OK: Greenbone Security Assistant is listening on port 443, which is > the default port. > Step 8: Checking nmap installation ... > WARNING: Your version of nmap is not fully supported: 7.70 > SUGGEST: You should install nmap 5.51 if you plan to use the nmap NSE > NVTs. > Step 10: Checking presence of optional tools ... > OK: pdflatex found. > OK: PDF generation successful. The PDF report format is likely to > work. > OK: ssh-keygen found, LSC credential generation for GNU/Linux targets > is likely to work. > OK: rpm found, LSC credential package generation for RPM based > targets is likely to work. > OK: alien found, LSC credential package generation for DEB based > targets is likely to work. > OK: nsis found, LSC credential package generation for Microsoft > Windows targets is likely to work. > > It seems like your OpenVAS-9 installation is OK. > > If you think it is not OK, please report your observation > and help us to improve this check routine: > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss > Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze > the problem. > > Best regards, > Daryn > > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss@wald.intevation.org > https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
_______________________________________________ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
