View Issue Details

IDProjectCategoryView StatusLast Update
0005233Kali Linux[All Projects] Kali Package Bugpublic2019-02-15 15:15
ReporterGvHAssigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status newResolutionopen 
Product Version2018.4 
Target VersionFixed in Version 
Summary0005233: After Kali upgrade OpenVAS targets with subnet definition don't work any longer
DescriptionAfter 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 Reproduceomp --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

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

2019-02-13 23:43

reporter   ~0010299

Same problem today.

rhertzog

2019-02-14 07:44

administrator   ~0010300

Can you report this to OpenVAS upstream developers?

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

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

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.

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