mikesplain / openvas-docker

A Docker container for Openvas
MIT License
768 stars 305 forks source link

Openvas Scanner 5.1.2 Hangs for Several Hours on Scans #209

Closed egerod closed 5 years ago

egerod commented 6 years ago

The docker image currently use Openvas Scanner 5.1.2, with contains a bug that causes scans to hang at 1% completion for several hours while consuming 100% CPU.

This bug have been fixed in 5.1.3, so updating to the new release should fix the issue.

Details:

boarnoah commented 6 years ago

This explains whats going on, I spent a few hours thinking it was my local network.

I notice in the linked thread they mention that OpenVas on Kali's repositories is updated with the fix. Haven't had any luck getting it to work there myself. Did you by any chance check it out too @egerod ?

egerod commented 6 years ago

@boarnoah no, haven't looked at fixing the current image, as I build an extra layer on the image, I was able to revert to an old image.

rowanruseler commented 6 years ago

This is easily resolved:

docker exec -it openvas bash
apt update
apt upgrade
apt-cache policy openvas9-scanner

should result in:

openvas9-scanner:
  Installed: 5.1.3-1
  Candidate: 5.1.3-1
  Version table:
 *** 5.1.3-1 500
        500 http://ppa.launchpad.net/mrazavi/openvas/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status

worked after that for me.

dbellavista commented 6 years ago

Thank you very much! A rebuild should fix it, right @mikesplain ?

samos123 commented 6 years ago

would be great if the docker image could get pushed with this latest patch. I seem to have hit the same isssue and the workaround worked fine.

mwild1 commented 5 years ago

It looks like the image was updated with 5.1.3 and this issue can be closed :+1:

fredairic[bot] commented 5 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions.

fredairic[bot] commented 5 years ago

This issue has been automatically closed because it has not had recent activity. Issue creator may reopen if the issue still exists. Thank you for your contributions.