search

greenbone / gvmd

Greenbone Vulnerability Manager - The database backend for the Greenbone Community Edition
GNU Affero General Public License v3.0
281 stars 153 forks source link

CSV Hosts filtered report contains wrong data when Overrides are applied #1303

Open bitmind opened 4 years ago

bitmind commented 4 years ago

Expected behavior

CSV Hosts report should contain the same data showed in web interface.

Actual behavior

For some hosts, severity level is "7.5 High" in web interface (which is correct, according to detected vulnerabilities and overrides applied). However, when generating the CSV export, severity for those host is calculated as "0.0 None" which is not correct.

Steps to reproduce

  1. Execute a Scan task
  2. Create an Override screen3791
  3. Go to Report > Hosts tab
  4. Filter the report with "Apply Overrides = Yes" and severity "Log=Yes". screen3787
  5. Verify hosts severities and number of vulnerabilities. screen3788
  6. Download the filtered report. Format "CSV Hosts" screen3789
  7. Open the csv file and compare the results screen3790

GVM versions

gsa: 8.0.0

gvm: 8.0.0

openvas-scanner: 6.0.0

gvm-libs:

Environment

Operating system: CentOS Linux release 7.7.1908 (Core) - 3.10.0-1062.9.1.el7.x86_64 greenbone/gsa#1 SMP Fri Dec 6 15:49:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Installation method / source: packages

cfi-gb commented 3 years ago

@greenbone/gvm-dev Please move / transfer this issue to https://github.com/greenbone/gvmd as this isn't an issue in GSA.

But not even sure if this is an issue at all or if only a different filter is used for the export vs. the one for showing the results in the GUI.

cfi-gb commented 3 years ago

@bitmind :

gsa: 8.0.0 gvm: 8.0.0 openvas-scanner: 6.0.0

Looks like outdated components as well:

https://community.greenbone.net/t/gvm-10-old-old-stable-initial-release-2019-04-05/208

Please update to more recent versions and try again to make sure this isn't an issue in older releases which are already fixed.

bjoernricks commented 3 years ago

As @cfi-gb already mentioned please update to a current supported release. Your components our outdated and therefore this issue might be fixed already.