Checking scan engine version

[Ainvar]

I have inherited a Greenbone Community Edition installation with no warning and less training. I am seeing the Severity 10.0 message that the scan engine is out of date. I figured out how to update the VTs and such, but I’m clearly missing how to update the scan engine as that error continues.

I’m sure the answer is in the manual, but I’ll be switched if I can find a clear answer. Anyone have a moment to point me in the right direction? I’d be much obliged.

[rippledj]

Updating the scan engine depends on how you installed it.

If you used the source code, then download the new source code packages from GitHub page and re-install. I guess only openvas-scanner package as per the source code instructions.

For docker containers see this post or simply pull the new containers and put them up as per the Greenbone Docker containers workflow instructions

Scan has Report Outdated finding on newly provisioned Greenbone Community Containers

Hiya, I have a setup where I use cloud-init to run the setup instructions from Greenbone Community Containers 22.4 - Greenbone Community Documentation, so that I can provision a new scanning instance which comes up with the latest docker images and is ready to scan. Here’s the relevant section of the cloud-init: runcmd: # Get the Greenbone CE docker-compose file and scripts - curl -f -L https://raw.githubusercontent.com/greenbone/docs/v23.6.1/src/_static/docker-compose-22.4.yml -o /home/green…

[cfi]

@rippledj

I guess only openvas-scanner package as per the source code instructions.

Note that all components (e.g. gvmd, gsa, gsad and especially gvm-libs and ospd-openvas) should be updated and kept up to date for reliable vulnerability scanning and reporting.