Greenbone's VT Release Process


Before we use any new/updated VTs, we always run them through openvas-nasl to ensure that nothing has been broken that could affect other NVTs

We see - quite regularly - NVTs with little mistakes - undeclared variables etc.
I was wondering whether it would be possible for the NVTs to be put through some kind of CI pipeline that runs them through openvas-nasl prior to release - to stop these issues from being sent to the wider public.

1 Like

Thanks for the heads up!
We do already put the community feed through a pipline, but are always greatful for pointers if we missed something.

1 Like

Ah great - thank you - these are the issues we’ve found:

/tmp/nvts/2010/host_summary.nasl:  script_oid("");
lib  nasl-Message: 13:33:57.168: [969](2019/google/gb_google_chrome_stable-channel-update-for-desktop_18-2019-09_lin.nasl)( The variable nesPort was not declared
Error while processing 2019/google/gb_google_chrome_stable-channel-update-for-desktop_18-2019-09_lin.nasl.
1 errors found
lib  nasl-Message: 13:33:57.183: [978](2019/google/gb_google_chrome_stable-channel-update-for-desktop_18-2019-09_macosx.nasl)( The variable nesPort was not declared
Error while processing 2019/google/gb_google_chrome_stable-channel-update-for-desktop_18-2019-09_macosx.nasl.
1 errors found
lib  nasl-Message: 13:33:57.198: [987](2019/google/gb_google_chrome_stable-channel-update-for-desktop_18-2019-09_win.nasl)( The variable nesPort was not declared
Error while processing 2019/google/gb_google_chrome_stable-channel-update-for-desktop_18-2019-09_win.nasl.
1 errors found
lib  nasl-Message: 13:33:57.317: [1013](2019/microsoft/gb_ms_kb4522007.nasl)( The variable CPE was not declared
Error while processing 2019/microsoft/gb_ms_kb4522007.nasl.
1 errors found
1 Like

Our patches are attached to this comment

gb_ms_kb4522007_cpe.patch (432 Bytes) gb_google_chrome_stable-channel-update-for-desktop_18-2019-09_win_nesport.patch (541 Bytes) gb_google_chrome_stable-channel-update-for-desktop_18-2019-09_macosx_nesport.patch (547 Bytes) gb_google_chrome_stable-channel-update-for-desktop_18-2019-09_lin_nesport.patch (541 Bytes)

Hello alexxq,

Thanks for your effort, we have already fixed the issues and updated VTs will be available in next feed update.

Antu Sanadi

1 Like

Thanks Antu,

Just for my own interest, could you let me know whether you will be running new/updated NVTs through openvas-nasl-lint pre-release in the future? It’d be great to catch these issues earlier - whilst these particular issues are relatively benign, they could cause more issues in the future



Hi Alex,

Yes, sure will run openvas-nasl-lint.


1 Like