View Issue Details

IDProjectCategoryView StatusLast Update
0005233Kali LinuxKali Package Bugpublic2019-09-04 12:37
ReporterGvH Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionopen 
Product Version2018.4 
Summary0005233: After Kali upgrade OpenVAS targets with subnet definition don't work any longer
Description

After upgrading Kali to 2019.1 we have problem with OpenVAS. Existing targets with a subnet definition (e.g. 10.0.0.0/24) is considered invalid. Creating new targets fails, both from CLI and through GSA webinterface.

Main problem is that existing targets are no longer valid. In GSA the number op IPs is -1 for these targets.
OpenVAS itself isn't updated.

Distributor ID: Kali
Description: Kali GNU/Linux Rolling
Release: 2019.1
Codename: n/a

openvas/kali-rolling,now 9.0.3kali1 all [installed]

Steps To Reproduce

omp --config-file=/home/kali/.openvas_adm --details --xml '
<create_target>
<name>test16</name>
<hosts>1.1.1.1/24</hosts>
</create_target>'
<create_target_response status_text="Error in host specification" status="400"></create_target_response>

The problem depends on the position of '/'. If '/' is the 12th or higher character there is no problem.
So:
10.0.1.1/24 --> Fails
10.10.1.1/24 --> Fails
10.10.10.1/24 --> Fails
10.10.10.1/24 --> Fails
10.10.10.10/24 --> no problem. '/' is 12th character
10.10.1.10/24 --> Fails
10.10.1.100/24 --> no problem
192.168.1.1-254 --> no problem

Activities

GvH

GvH

2019-02-04 14:34

reporter   ~0010251

I've found a workaround for old targets that have problems after the upgrade:

  • Generate a list of all IP-adressses in the subnet for example with 'nmap -sL 10.1.1.0/24'
  • Stop openvas-manager
  • Open SQLite3 databse: sqlite3 /var/lib/openvas/mgr/tasks.db
  • Update table targets. E.g. update targets set hosts = '<IP-list>' where name = '<targetname>'
  • Start openvas-manager
MelroyB

MelroyB

2019-02-13 23:43

reporter   ~0010299

Same problem today.

rhertzog

rhertzog

2019-02-14 07:44

administrator   ~0010300

Can you report this to OpenVAS upstream developers?

GvH

GvH

2019-02-14 12:12

reporter   ~0010302

This problem is already known in the Greenbone Community. See https://community.greenbone.net/t/error-in-host-specification/1484.

rhertzog

rhertzog

2019-02-14 15:03

administrator   ~0010306

Nice, but last I checked, they were using a bug tracker on sourceforge. Or is there a better way to contact the upstream developers ?

GvH

GvH

2019-02-15 15:15

reporter   ~0010310

I don't know what is the best way to contact OpenVAS upstream developers. I'm just a simple enduser. The only place I found to report bugs where this Kali Linux Bug Tracker and the Greenbone community. I can't find an OpenVAS bug tracker on Sourceforge, sorry.

kali-bugreport

kali-bugreport

2019-03-16 08:26

reporter   ~0010425

Source code and issue trackers for all components seems to have moved to github: https://github.com/greenbone/

g0tmi1k

g0tmi1k

2019-09-04 12:37

administrator   ~0011017

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling <= 2018.4), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/)?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup?
For more information, please read: https://kali.training/topic/filing-a-good-bug-report/

Issue History

Date Modified Username Field Change
2019-02-01 15:03 GvH New Issue
2019-02-04 14:34 GvH Note Added: 0010251
2019-02-13 23:43 MelroyB Note Added: 0010299
2019-02-14 07:44 rhertzog Note Added: 0010300
2019-02-14 12:12 GvH Note Added: 0010302
2019-02-14 15:03 rhertzog Note Added: 0010306
2019-02-15 15:15 GvH Note Added: 0010310
2019-03-16 08:26 kali-bugreport Note Added: 0010425
2019-09-04 12:37 g0tmi1k Note Added: 0011017
2019-09-04 12:37 g0tmi1k Status new => closed