remote-detect-MDNS.nasl error

Vulnerability Tests
1

Hi, I’m scanning a target and got the following error message:

(remote-detect-MDNS.nasl:66) In function 'grabHostInfos()': Missing argument: str_replace(string: s, find: f, replace: r [,count: c])
(remote-detect-MDNS.nasl:73) In function 'grabHostInfos()': make_array: bad value type 0 for arg #2
(remote-detect-MDNS.nasl:94) In function 'grabCpuInfos()': get_array_elem: requesting character after end of string stringa (144 >= 109)
(remote-detect-MDNS.nasl:101) In function 'grabCpuInfos()': make_array: bad value type 0 for arg #4

The reply from the target that being processed is:

004a818300010000000100000c5f776f726b73746174696f6e045f746370056c6f63616c00000c0001000006000100000a24004001610c726f6f742d73657276657273036e657400056e73746c640c766572697369676e2d67727303636f6d007877da5a000007080000038400093a8000015180

2

Hi @panajo1017 :slight_smile:

I have a question about your setup in order to see if it helps anyone to track it down, and here’s a template you can use:

GVM versions

gsad: (‘gsad --version’)
gvmd: (‘gvmd --version’)
openvas-scanner: (‘openvas --version’, in older GVM versions < 11: ‘openvassd --version’)
gvm-libs:

Environment

Operating system:
Kernel: (‘uname -a’)
Installation method / source:

Thanks!

3

Hi, this is just an error in the nasl script itself, not depending on the setup.

4

Please note that these are no real errors but more or less cosmetic warnings due to some possible too lax response length checks in this aged and 3rdparty detection script.

The messages doesn’t have any affect on the functionality of the VT or the scan itself.

Nevertheless i have created an internal task to check if the response checks can be improved. Please do note that this currently has very low priority and a community provided patch might speed up a progress a lot.

3 Likes
5

Yes, that’s true. Just reporting because the warning message raised in the scanner log.

1 Like
6

Ah, yes. No worries and thanks a lot for posting such warnings, we really appreciate that because they might only happen when scanning specific environments or similar.

Just wanted to point out that messages like this are in most cases harmless and doesn’t affect a scan in general.

1 Like