Containers for running the Greenbone Vulnerability Manager. Run as a single container with all services or separate single applications containers via docker-compose.
License: GNU Affero General Public License v3.0
Hello,
thanks for the great work, i tried to restart the Container today and run in to an Issue " Exited with Code 1 - User exists already". Here are the last lines of the Logfiles:
openvas_1 | Starting Greenbone Vulnerability Manager...
openvas_1 | Waiting for gvmd
openvas_1 | User1
openvas_1 | admin
openvas_1 | User2
openvas_1 | Time to fixup the gvm accounts.
openvas_1 | Creating new user User1 with supplied password.
openvas_1 | If no password supplied on startup, then the default password is admin
openvas_1 | ...... Don't do that .....
openvas_1 | Creating Greenbone Vulnerability Manager admin user as User1
openvas_1 | User exists already.
openvas_openvas_1 exited with code 1
Here is a a part of my compose File:
environment:
- "USERNAME=User1"
- "PASSWORD=**********"
- "RELAYHOST=172.17.0.1"
- "SMTPPORT=25"
- "REDISDBS=512" # number of Redis DBs to use
- "QUIET=false" # dump feed sync noise to /dev/null
- "NEWDB=false" # only use this for creating a blank DB
- "SKIPSYNC=true" # Skips the feed sync on startup.
- "RESTORE=false" # This probably not be used from compose... see docs.
- "DEBUG=false" # This will cause the container to stop and not actually start gvmd
- "HTTPS=false" # wether to use HTTPS or not
- "GMP=false" # to enable see docs
Also i had the Issue, that when i set SKIPSYNC=true it doenst seem to work. If i delete SKIPSYNC he also syncs NVT's
After a scan is finished and report is generated - when I click on it - I just see the green dragon? head (the logo of openvas) blinking for about 1 minute and then I get an error:
Error while loading Results for Report 234bda13-3464-4e26-944c-308646df306b
Please try again.
While the report is trying to load I see in top "postgres: gvm gvmd [local] SELECT" at 100% CPU, the disk utilization is fine around 2%, the drive is SSD.
Any ideas what I can test, look into?
My Raspberry pi report this error:
ubuntu@ubuntu:~$ sudo docker run --detach --publish 8080:9392 -e PASSWORD="9132059091320590" --volume openvas:/data --name openvas immauss/openvas
Unable to find image 'immauss/openvas:latest' locally
latest: Pulling from immauss/openvas
docker: no matching manifest for linux/arm/v7 in the manifest list entries.
See 'docker run --help'.
There is no support for raspberry?
Hello
I was just testing the gvm-cli tools and found a bug that was solved: https://community.greenbone.net/t/authentication-failed-with-gvm-cli-same-creds-work-on-the-web-ui/9424
Just pip3 install gvm-tools --upgrade and it will be fixed.
Regards
Using latest, after I try to modify a cloned scan config I get
Whole-only families must include entire family and be growing
Is seems a solved issue in OpenVAS (https://community.greenbone.net/t/error-whole-only-families-must-include-entire-family-and-be-growing/9169)
After the error not all scan configs are saved, for example the selection of active families is not.
I use the https://github.com/greenbone/gvm-tools && https://gvm-tools.readthedocs.io/en/latest/index.html .
My script creates targets, tasks, start them and in the end exports the report. So it's an automated process. It uses the sock to connect to GVM this is the default and recommended: https://gvm-tools.readthedocs.io/en/latest/connectiontypes.html#using-a-unix-domain-socket
Well with the lastest image gvmd.sock doesn't exist:
root@a32a5611b731:~# find / -name "gvmd.sock"
root@a32a5611b731:~#
I'll leave this up to the maintainer to decide if it should go into the readme, but it was certainly something we struggled to get working, how to create other super admins - we have the answers in-case someone comes looking for it
You will need to find the name of the docker container first
docker ps
Then run the following
docker exec -it <name> bash
su - gvm
gvmd --create-user=MySecondSuperAdmin -v --role="Super Admin"
This will result in a message saying that the user has been created along with the new password - take note of this before proceeding.
If you have already create a normal admin and would like to become a super admin, do the following
docker exec -it <name> bash
su - gvm
gvmd --create-user=MyUser2 -v --role="Super Admin"
gvmd –-delete-user=MyUser --inheritor=MyUser2
gvmd --create-user=MyUser -v --role="Super Admin"
gvmd –-delete-user=MyUser2 --inheritor=MyUser
Ensuring you take note of the password for the 2nd create user!
Container seems not to start correctly (trying restarts and quitting after a bunch of restarts):
openvas_1 | Redis ready.
openvas_1 | Fixing local/share ...
openvas_1 | cp: cannot create regular file '/data/local-share/gvm/gvmd/global_schema_formats/787a4a18-dabc-11df-9486-002264764cea/rnc.xsl': File exists
openvas_1 | 8:C 14 Jun 2021 12:59:14.809 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
openvas_1 | 8:C 14 Jun 2021 12:59:14.809 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=8, just started
openvas_1 | 8:C 14 Jun 2021 12:59:14.809 # Configuration loaded
openvas_1 | Wait for redis socket to be created...
openvas_1 | Testing redis status...
openvas_1 | Redis ready.
openvas_1 | Fixing local/share ...
openvas_1 | cp: cannot create regular file '/data/local-share/gvm/gvmd/global_schema_formats/787a4a18-dabc-11df-9486-002264764cea/rnc.xsl': File exists
openvas_1 | 10:C 14 Jun 2021 12:59:21.048 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
openvas_1 | 10:C 14 Jun 2021 12:59:21.048 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=10, just started
openvas_1 | 10:C 14 Jun 2021 12:59:21.048 # Configuration loaded
openvas_1 | Wait for redis socket to be created...
openvas_1 | Testing redis status...
openvas_1 | Redis ready.
/data/local-share/gvm/gvmd/global_schema_formats/787a4a18-dabc-11df-9486-002264764cea/rnc.xsl indeed exists in/on the volume
docker-compose.yml:
version: '3'
services:
openvas:
image: immauss/openvas:21.04.01
restart: always
volumes:
#- /data/openvas/data:/data
- ./data:/data
ports:
- "8088:9392"
environment:
- RELAYHOST=10.0.0.20
- QUIET=trueHi immauss,
great App running on docker. I'm not a specialist concerning docker but seems that everything is running except SECInfos.I get on SecInfo WebUI this message "The SCAP database is required"
Running docker logs brings me:
md manage:WARNING:2020-10-21 16h34.09 utc:1378: open_secinfo_lockfile: failed to open lock file '/tmp/gvm-sync-scap': Permission denied
md manage:WARNING:2020-10-21 16h34.09 utc:1379: open_secinfo_lockfile: failed to open lock file '/tmp/gvm-sync-cert': Permission denied
md manage:WARNING:2020-10-21 16h34.19 utc:1382: open_secinfo_lockfile: failed to open lock file '/tmp/gvm-sync-scap': Permission denied
md manage:WARNING:2020-10-21 16h34.19 utc:1385: open_secinfo_lockfile: failed to open lock file '/tmp/gvm-sync-cert': Permission denied
and yes,after first start i'm waiting about 1 hour after finishing sync feeds.
Any idea/hint?
Thanks in advance
Mark
There seems to be a bug tagging the latest tag, currently it points to 21.4.1 instead of 21.4.3
Latest:
immauss/openvas:latest
DIGEST:sha256:55eac39bce168a1a7400bd3cd79cfaf7e79b17c71c34df33ba31cce0dcd12f12
Tag 21.4.1
immauss/openvas:21.4.1
DIGEST:sha256:55eac39bce168a1a7400bd3cd79cfaf7e79b17c71c34df33ba31cce0dcd12f12
Tag 21.4.3
immauss/openvas:21.4.3
DIGEST:sha256:11872ad0c9919a903c11ed6338063bfb067b8cd01c01a4df22967397ddf53f11
Tried your new docker container 20.08.05, having issues:
today at 8:26 AM md manage: INFO:2021-02-08 07h26.25 utc:31631: update_scap: Updating data from feed
today at 8:26 AM md manage:WARNING:2021-02-08 07h26.25 utc:31631: update_scap_cpes: No CPE dictionary found at /usr/local/var/lib/gvm/scap-data/official-cpe-dictionary_v2.2.xml
today at 8:26 AM md manage:WARNING:2021-02-08 07h26.35 utc:31640: update_scap: No SCAP db present, rebuilding SCAP db from scratch
today at 8:26 AM md manage: INFO:2021-02-08 07h26.35 utc:31640: update_scap: Updating data from feed
I tried from scratch and with https://github.com/immauss/gvm-var-lib, didn't help
Failed to find config 'daba56c8-73ec-11df-a475-002264764cea'
Is there something on my side that I'm doing wrong?
My compose file:
openvas:
container_name: openvas
environment:
- PASSWORD=xyz
- HTTPS=false
- RELAYHOST=mail.zzz
- SKIPSYNC=true
hostname: openvas.zzz
image: immauss/openvas:20.08.05
labels:
- com.centurylinklabs.watchtower.enable=true
ports:
- 8083:9392
restart: always
volumes:
- /opt/docker/openvas:/data
BTW: Thanks for your work!
Is there any way to configure gvmd with tls? I really need it for my remote operations..
Unsure if you were aware, but it seems that during spin-up of the container, PQexec runs into an error with sql_exec.
See log file below:
md manage: INFO:2020-09-16 17h50.09 utc:679: Updating user OVAL definitions.
md manage: INFO:2020-09-16 17h50.09 utc:679: Updating CVSS scores and CVE counts for CPEs
md manage: INFO:2020-09-16 17h50.37 utc:679: Updating CVSS scores for OVAL definitions
md manage: INFO:2020-09-16 17h50.39 utc:679: Updating placeholder CPEs
md manage: INFO:2020-09-16 17h50.46 utc:679: update_scap: Updating SCAP info succeeded
md manage:WARNING:2020-09-16 17h50.46 utc:679: sql_exec_internal: PQexec failed: ERROR: relation "cert_bund_advs" does not exist
LINE 1: SELECT EXISTS (SELECT * FROM cert_bund_advs WHERE creation_...
^
(7)
md manage:WARNING:2020-09-16 17h50.46 utc:679: sql_exec_internal: SQL: SELECT EXISTS (SELECT * FROM cert_bund_advs WHERE creation_time > coalesce (CAST ((SELECT value FROM meta WHERE name = 'cert_check_time') AS INTEGER), 0));
md manage:WARNING:2020-09-16 17h50.46 utc:679: sql_x_internal: sql_exec_internal failed
Any ideas?
When trying to browse through the reports generated it's very slow to retrieve the results. Just sorting the Severity from high to low takes 30+ seconds to complete and during this process I can see that postgres is running at 100 % CPU. I believe this is not an issue related to this dockerization of OpenVAS, but maybe something related to OpenVAS itself? Do you see the same?
It is probably not recommended to change the default admin/admin credentials in the docker-compose file, but that's what I did since I generally don't like to leave the username as 'admin'.
When changing the docker-compose file to use a different user/password, the default admin user is also setup with the default 'admin' password. I didn't realize this until i ran a scan against the OpenVAS host and received a severity score of 10.
Hi, for some reason when I run the suggested command to start the container as shown below, the docker image immediately exits. Is there something Im missing out? Thanks!
Hey,
From a fresh install noticed this one. I might very well be the only one using it! :)
The gvm-pyshell defaults to searching for /var/run/gvmd.sock but it's up in /usr/local/var/run/gvmd.sock
I've create a PR, but you might want to do it differently. No hassle
Hello!
I was wondering if this container has the SMB requirements in order to scan Windows hosts?
See
https://greenbone.github.io/docs/gvm-21.04/index.html#openvas-smb
I am in the process of deploying this image now but wanted to ask just in case it wasn't in here yet.
After entering the correct user data I see briefly (1 second) flash the interface,
I am redirected back to the login screen and should enter my password again.
I can’t get into the user interface of GVM.
This is in the latest version of gvm which is not yet pushed to my github. Documenting here so I can keep track of it.
Clicking on the link for past scans from the Task list leads to the following error message:
TypeError: Cannot read property 'scan_run_status' of undefined
in mG
in tbody
in t
in styled.tbody
in table
in Unknown
in t
in Styled(StripedTable)
in div
in Unknown
in t
in Styled(Layout)
in n
in Unknown
in div
in Unknown
in t
in Layout
in section
in tr
in n
in div
in Unknown
in t
in Layout
in n
in w
in Unknown
in n
in n
in w
in withRouter(Connect(n))
in n
in Unknown
in l
in w
in Unknown
in a
in n
in Unknown
in Tg
in n
in Unknown
in w
in Unknown
in t
in t
in n
in main
in t
in Main
in Unknown
in t
in withLayout(Main)
in div
in Unknown
in t
in Styled(Layout)
in n
in withRouter(n)
in Unknown
in n
in w
in withRouter(Connect(n))
in Unknown
in n
in w
in withRouter(Connect(n))
in Unknown
in t
in t
in Unknown
in Unknown
in n
in w
in l
in n
in n
TypeError: Cannot read property 'scan_run_status' of undefined
at mG (http://ames:9392/static/js/main.bc743b66.chunk.js:1:1448862)
at Gi (http://ames:9392/static/js/2.f7d69170.chunk.js:2:684338)
at bc (http://ames:9392/static/js/2.f7d69170.chunk.js:2:730750)
at us (http://ames:9392/static/js/2.f7d69170.chunk.js:2:723277)
at cs (http://ames:9392/static/js/2.f7d69170.chunk.js:2:723202)
at Zc (http://ames:9392/static/js/2.f7d69170.chunk.js:2:720211)
at http://ames:9392/static/js/2.f7d69170.chunk.js:2:671596
at t.unstable_runWithPriority (http://ames:9392/static/js/2.f7d69170.chunk.js:2:747183)
at Yo (http://ames:9392/static/js/2.f7d69170.chunk.js:2:671305)
at Vo (http://ames:9392/static/js/2.f7d69170.chunk.js:2:671541)
Updated by watchtower ;-( using latest image, reverting to 21.4.3 for now
Trying 'latest' image (33f5854b20e4) breaks things:
openvas | 8:C 01 Sep 2021 17:47:24.991 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
openvas | 8:C 01 Sep 2021 17:47:24.991 # Redis version=5.0.3, bits=64, commit=00000000, modified=0, pid=8, just started
openvas | 8:C 01 Sep 2021 17:47:24.991 # Configuration loaded
openvas | Wait for redis socket to be created...
openvas | Testing redis status...
openvas | Redis ready.
openvas | Fixing Database folder...
openvas | ln: failed to create symbolic link '/var/lib/postgresql/12/main': No such file or directory
Hello.
Redis down. I suggest adding redis logs to the general output to simplify debugging
problem start from
/usr/local/var/log/gvm/openvas.log
sd main:MESSAGE:2021-08-22 01h01.54 utc:2299019: Vulnerability scan e39b738a-91ca-4511-943a-c9e0100d5a21 finished for host 10.32.8.61 in 456.57 seconds
sd main:MESSAGE:2021-08-22 01h01.55 utc:2312744: Vulnerability scan e39b738a-91ca-4511-943a-c9e0100d5a21 started for host: 10.32.9.200
libgvm util:CRITICAL:2021-08-22 01h02.00 utc:2306522: No redis DB available
libgvm util:CRITICAL:2021-08-22 01h02.00 utc:2312910: No redis DB available
libgvm util:CRITICAL:2021-08-22 01h02.00 utc:2312910: get_redis_ctx: redis connection error to /run/redis/redis.sock: Connection refused
libgvm util:CRITICAL:2021-08-22 01h02.00 utc:2312910: get_redis_ctx: redis connection error to /run/redis/redis.sock: Connection refused
libgvm util:CRITICAL:2021-08-22 01h02.00 utc:2312847: get_redis_ctx: redis connection error to /run/redis/redis.sock: Connection refused
libgvm util:CRITICAL:2021-08-22 01h02.00 utc:2312799: No redis DB available
libgvm util:CRITICAL:2021-08-22 01h02.00 utc:2312298: No redis DB available
libgvm util:CRITICAL:2021-08-22 01h02.00 utc:2312892: No redis DB available
libgvm util:CRITICAL:2021-08-22 01h02.00 utc:2301148: get_redis_ctx: redis connection error to /run/redis/redis.sock: Connection refused
sd main:MESSAGE:2021-08-22 01h02.00 utc:2301148: Plugin '1.3.6.1.4.1.25623.1.0.18186' missing from nvticache.
libgvm util:CRITICAL:2021-08-22 01h02.00 utc:2301148: get_redis_ctx: redis connection error to /run/redis/redis.sock: Connection refused
sd main:MESSAGE:2021-08-22 01h02.00 utc:2301148: Plugin '1.3.6.1.4.1.25623.1.0.100329' missing from nvticache.
root@3e8093e79b67:/# tail /usr/local/var/log/gvm/*
==> /usr/local/var/log/gvm/gsad.log <==
gsad gmp:MESSAGE:2021-08-24 10h13.39 GMT:842: Authentication success for 'admin' from 172.17.0.1
gsad gmp:MESSAGE:2021-08-24 10h13.50 GMT:842: Authentication success for 'admin' from 172.17.0.1
gsad gmp:MESSAGE:2021-08-24 12h20.19 GMT:842: Authentication success for 'admin' from 172.17.0.1
gsad gmp:MESSAGE:2021-08-24 12h52.12 GMT:842: Authentication success for 'admin' from 172.17.0.1
gsad gmp:MESSAGE:2021-08-24 13h02.21 GMT:842: Authentication success for 'admin' from 172.17.0.1
gsad gmp:MESSAGE:2021-08-24 16h11.36 GMT:842: Authentication success for 'admin' from 172.17.0.1
gsad gmp:MESSAGE:2021-08-24 16h11.37 GMT:842: Authentication success for 'admin' from 172.17.0.1
gsad gmp:MESSAGE:2021-08-25 07h46.10 GMT:842: Authentication success for 'admin' from 172.17.0.1
gsad gmp:MESSAGE:2021-08-25 08h20.17 GMT:842: Authentication success for 'admin' from 172.17.0.1
gsad gmp:MESSAGE:2021-08-25 09h14.10 GMT:842: Authentication success for 'admin' from 172.17.0.1
==> /usr/local/var/log/gvm/gvmd.log <==
event task:MESSAGE:2021-08-25 09h16.15 UTC:2275398: Task XXX.XXX.0.0/20 Clone 1 (d34e25f3-86d6-4e88-a7a6-778b01633dca) has been modified by admin
event target:MESSAGE:2021-08-25 09h17.25 UTC:2275503: Target XXX.XXX.8.0/21 (ec39dcaf-19d9-4d02-9d0a-a17c57297047) has been modified by admin
event task:MESSAGE:2021-08-25 09h17.57 UTC:2275622: Task XXX.XXX.0.0/21 (d34e25f3-86d6-4e88-a7a6-778b01633dca) has been modified by admin
event task:MESSAGE:2021-08-25 09h18.12 UTC:2275681: Task XXX.XXX.8.0/21 (d34e25f3-86d6-4e88-a7a6-778b01633dca) has been modified by admin
event task:MESSAGE:2021-08-25 09h18.15 UTC:2275710: Status of task XXX.XXX.8.0/21 (d34e25f3-86d6-4e88-a7a6-778b01633dca) has changed to Requested
event task:MESSAGE:2021-08-25 09h18.15 UTC:2275710: Task XXX.XXX.8.0/21 (d34e25f3-86d6-4e88-a7a6-778b01633dca) has been requested to start by admin
md manage:WARNING:2021-08-25 09h18.17 UTC:2275713: Could not connect to Scanner at /var/run/ospd/ospd.sock
md manage:WARNING:2021-08-25 09h18.17 UTC:2275713: OSP start_scan be40db58-7e8f-4054-820e-7103ef2dce2b: Could not connect to Scanner
event task:MESSAGE:2021-08-25 09h18.17 UTC:2275713: Status of task XXX.XXX.8.0/21 (d34e25f3-86d6-4e88-a7a6-778b01633dca) has changed to Done
event task:MESSAGE:2021-08-25 09h18.17 UTC:2275713: Status of task XXX.XXX.8.0/21 (d34e25f3-86d6-4e88-a7a6-778b01633dca) has changed to Interrupted
==> /usr/local/var/log/gvm/openvas.log <==
sd main:MESSAGE:2021-08-24 17h27.23 utc:2183516: Vulnerability scan 2f9482c2-7743-4bb0-82a4-5f50e029538b finished for host XXX.XXX.5.10 in 2334.93 seconds
sd main:MESSAGE:2021-08-24 17h27.23 utc:2256581: Vulnerability scan 2f9482c2-7743-4bb0-82a4-5f50e029538b finished for host XXX.XXX.10.64 in 219.40 seconds
sd main:MESSAGE:2021-08-24 17h27.23 utc:2240376: Vulnerability scan 2f9482c2-7743-4bb0-82a4-5f50e029538b finished for host XXX.XXX.5.14 in 973.39 seconds
sd main:MESSAGE:2021-08-24 17h27.23 utc:2255002: Vulnerability scan 2f9482c2-7743-4bb0-82a4-5f50e029538b finished for host XXX.XXX.5.15 in 366.94 seconds
libgvm util:CRITICAL:2021-08-24 17h27.23 utc:2258391: get_redis_ctx: redis connection error to /run/redis/redis.sock: Connection refused
sd main:MESSAGE:2021-08-24 17h27.23 utc:2258391: Plugin '1.3.6.1.4.1.25623.1.0.100795' missing from nvticache.
sd main:MESSAGE:2021-08-24 17h27.23 utc:2258391: Vulnerability scan 2f9482c2-7743-4bb0-82a4-5f50e029538b finished for host XXX.XXX.4.222 in 56.71 seconds
libgvm util:CRITICAL:2021-08-24 17h27.23 utc:2258234: get_redis_ctx: redis connection error to /run/redis/redis.sock: Connection refused
sd main:MESSAGE:2021-08-24 17h27.23 utc:2258234: Plugin '1.3.6.1.4.1.25623.1.0.80092' missing from nvticache.
sd main:MESSAGE:2021-08-24 17h27.23 utc:2258234: Vulnerability scan 2f9482c2-7743-4bb0-82a4-5f50e029538b finished for host XXX.XXX.8.62 in 69.04 seconds
==> /usr/local/var/log/gvm/ospd-openvas.log <==
OSPD[826] 2021-08-24 17:27:12,797: INFO: (ospd.ospd) 2f9482c2-7743-4bb0-82a4-5f50e029538b: Scan interrupted.
OSPD[826] 2021-08-24 17:27:13,359: INFO: (ospd.ospd) 2f9482c2-7743-4bb0-82a4-5f50e029538b: Scan process is dead and its progress is 82
OSPD[826] 2021-08-24 17:27:13,367: INFO: (ospd.ospd) 2f9482c2-7743-4bb0-82a4-5f50e029538b: Scan interrupted.
OSPD[826] 2021-08-24 17:27:13,380: INFO: (ospd.ospd) 2f9482c2-7743-4bb0-82a4-5f50e029538b: Scan process is dead and its progress is 82
OSPD[826] 2021-08-24 17:27:13,380: INFO: (ospd.ospd) 2f9482c2-7743-4bb0-82a4-5f50e029538b: Scan interrupted.
OSPD[826] 2021-08-24 17:27:13,438: INFO: (ospd.ospd) 2f9482c2-7743-4bb0-82a4-5f50e029538b: Scan process is dead and its progress is 82
OSPD[826] 2021-08-24 17:27:13,439: INFO: (ospd.ospd) 2f9482c2-7743-4bb0-82a4-5f50e029538b: Scan interrupted.
OSPD[826] 2021-08-24 17:27:13,472: INFO: (ospd.ospd) 2f9482c2-7743-4bb0-82a4-5f50e029538b: Scan process is dead and its progress is 82
OSPD[826] 2021-08-24 17:27:13,472: INFO: (ospd.ospd) 2f9482c2-7743-4bb0-82a4-5f50e029538b: Scan interrupted.
OSPD[826] 2021-08-24 17:27:21,417: INFO: (ospd.main) Shutting-down server ...
Hello!
I just tried your docker container on my synology, as the old one I used hasn't been maintained for over 2 years.
At the beginning everything seems to be ok, but unfortunately I got this error in the end:
md manage: INFO:2020-05-28 14h54.15 utc:446: Updating OVAL data
md manage: INFO:2020-05-28 14h59.55 utc:446: Updating /usr/local/var/lib/gvm/scap-data/oval/5.10/org.mitre.oval/c/oval.xml
md manage: INFO:2020-05-28 14h59.56 utc:446: Updating /usr/local/var/lib/gvm/scap-data/oval/5.10/org.mitre.oval/m/oval.xml
md manage: INFO:2020-05-28 14h59.56 utc:446: Updating /usr/local/var/lib/gvm/scap-data/oval/5.10/org.mitre.oval/v/family/ios.xml
md manage: INFO:2020-05-28 14h59.59 utc:446: Updating /usr/local/var/lib/gvm/scap-data/oval/5.10/org.mitre.oval/v/family/pixos.xml
md manage: INFO:2020-05-28 14h59.59 utc:446: Updating /usr/local/var/lib/gvm/scap-data/oval/5.10/org.mitre.oval/p/oval.xml
md manage: INFO:2020-05-28 15h08.20 utc:446: Updating /usr/local/var/lib/gvm/scap-data/oval/5.10/org.mitre.oval/i/oval.xml
md manage: INFO:2020-05-28 15h08.23 utc:446: Updating /usr/local/var/lib/gvm/scap-data/oval/5.10/org.mitre.oval/v/family/macos.xml
md manage: INFO:2020-05-28 15h08.24 utc:446: Updating /usr/local/var/lib/gvm/scap-data/oval/5.10/org.mitre.oval/v/family/unix.xml
md manage: INFO:2020-05-28 15h08.55 utc:446: Updating /usr/local/var/lib/gvm/scap-data/oval/5.10/org.mitre.oval/v/family/windows.xml
md manage: INFO:2020-05-28 15h09.21 utc:446: Updating user OVAL definitions.
md manage: INFO:2020-05-28 15h09.21 utc:446: Updating CVSS scores and CVE counts for CPEs
md manage: INFO:2020-05-28 15h21.24 utc:446: Updating CVSS scores for OVAL definitions
md manage: INFO:2020-05-28 15h21.38 utc:446: Updating placeholder CPEs
md manage: INFO:2020-05-28 15h26.04 utc:446: sync_scap: Updating SCAP info succeeded
md manage:WARNING:2020-05-28 15h26.08 utc:446: sql_exec_internal: PQexec failed: ERROR: relation "cert_bund_advs" does not exist
LINE 1: SELECT EXISTS (SELECT * FROM cert_bund_advs WHERE creation_...
^
(7)
md manage:WARNING:2020-05-28 15h26.08 utc:446: sql_exec_internal: SQL: SELECT EXISTS (SELECT * FROM cert_bund_advs WHERE creation_time > coalesc
e (CAST ((SELECT value FROM meta WHERE name = 'cert_check_time') AS I
NTEGER), 0));
md manage:WARNING:2020-05-28 15h26.08 utc:446: sql_x_internal: sql_exec_internal failed
Webgui is reachable but I am not able to login, the site just refreshes:
gsad gmp:MESSAGE:2020-05-28 15h50.29 utc:478: Authentication success for 'admin' from 172.17.0.1
Can you help me here? :)
Using latest as of today (21.04.1), two different machines.
First startup took a couple of hours each (not expected based on previous experience).
Once it update it all, I started several scans. All do not give results.
Trying to debug the OpenVAS part it seems that no scanners are selected.
Going to the scanner setup in the scan profile, I see something is missing here...
inested of this, from a working setup
So basically, no scanners => no scan.
Thanks
You cannot use this image with Dockergen, as the image is not exposing any ports. Can you please add to the Dockerfile
EXPOSE 9392
Then, dockergen can create a configuration for it when it is behind a reverse proxy. It should have this in the Dockerfile anyway.
docker run -e RSYNC_PROXY -p 9392:9392 -p 9390:9390 -e GMP=9390 --name immauss-openvas -v openvas:/data immauss/openvas:latest
The login on the web with the user admin: admin does not work:
website message
The Greenbone Vulnerability Manager service is not responding. This could be due to system maintenance. Please try again later, check the system status, or contact your system administrator.
log message
==> /usr/local/var/log/gvm/gsad.log <==
gsad gmp:WARNING:2021-08-11 02h59.37 utc:985: Failed to connect to server at /usr/local/var/run/gvmd.sock: No such file or directory
gsad gmp:WARNING:2021-08-11 02h59.37 utc:985: Authentication failure for 'admin' from 172.168.1.23. Status was 1.
linux version
Linux CentoOS 7.9 - 3.10.0-1160.11.1.el7.x86_64 #1 SMP Fri Dec 18 16:34:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
docker version
Client: Docker Engine - Community
Version: 20.10.8
API version: 1.41
Go version: go1.16.6
Git commit: 3967b7d
Built: Fri Jul 30 19:55:49 2021
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.8
API version: 1.41 (minimum version 1.12)
Go version: go1.16.6
Git commit: 75249d8
Built: Fri Jul 30 19:54:13 2021
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.4.9
GitCommit: e25210fe30a0a703442421b0f60afac609f950a3
runc:
Version: 1.0.1
GitCommit: v1.0.1-0-g4144b63
docker-init:
Version: 0.19.0
GitCommit: de40ad0
When mailing the reports in PDF form I get the following error in the report email:
"This report exceeds the maximum length of 1048576 characters and thus was truncated." The email has no attachments. This error occurs when scanning /26 IP range. /27 IP ranges work fine.
I've modified your your start start.sh script in line :253 from
su -c "gvmd --osp-vt-update=/tmp/ospd.sock" gvm
to
su -c "gvmd --osp-vt-update=/tmp/ospd.sock --max-email-attachment-size=64000000 --max-email-include-size=64000000 --max-email-message-size=64000000" gvm
and deleted the old container plus volume and build a new container with $ docker-compose up -d
...but it seems that this doesn't work. When scanning the /26 range again the error persists.
The NEWDB environment variable is initially set to "false". This means if I don't set it explicitly to "true" in the container environment the code block in /start.sh creating a base DB from /usr/lib/base-db.xz is executed.
Is this intended? The normal case is that the database already exists.
After the last docker image release the container fails while updating:
Updating NVTs and other data
This could take a while if you are not using persistent storage for your NVTs
or this is the first time pulling to your persistent storage.
the time will be mostly dependent on your available bandwidth.
We sleep for 5 seconds between sync command to make sure everything closes
and it doesnt' look like we are connecting more than once.
Fine, ... we'll be quiet, but we warn you if there are errors
syncing the feeds, you'll miss them.
Pulling NVTs from greenbone
Pulling scapdata from greenbone
Unfortunately I have the quiet flag set.. :(
Portainer:
Status | Stopped for 1 minutes with exit code 1
Using 20.08.04.4.
Started with
docker run --detach --publish 2939:9392 -e PASSWORD="xHya3Usi" --volume openvas:/data --name openvas immauss/openvas
after creating the openvas volume.
It works but the password for the admin user is not set, it is the standard admin one.
Not a big deal since you can change it from the web interface, but maybe there's something wrong with the environment variables.
Hi,
I just pulled the image and started with:
docker run --detach -e PASSWORD="my_password" --volume openvas:/data --name openvas immauss/openvas
It took quite long to update the NVTs and had some strange events logged like:
md manage: INFO:2021-03-21 13h41.38 utc:2391: OSP service has different VT status (version 202103191122) from database (version 202103121134, 65858 VTs). Starting update ...
imd manage: INFO:2021-03-21 13h43.23 utc:2391: Updating VTs in database ... 92 new VTs, 197 changed VTs
md manage:WARNING:2021-03-21 13h43.25 utc:2391: update_nvts_from_vts: SHA-256 hash of the VTs in the database (ccb34ff4b6b4f10a1aa5ded9e23c2772ea70797a2d825908347cabd219fbeb4e) does not match the one from the scanner (16cbd2fbcd8563b8cec70fdc9a3ef21b23908f4fcc8838f428ab82f19608fda5).
md main:MESSAGE:2021-03-21 13h43.25 utc:2391: Rebuilding NVTs because integrity check failed
but after this update seems to be done so far:
md manage: INFO:2021-03-21 13h53.52 utc:2391: Updating VTs in database ... 66027 new VTs, 0 changed VTs
md manage: INFO:2021-03-21 13h53.55 utc:2391: Updating VTs in database ... done (66027 VTs).
md main:MESSAGE:2021-03-21 13h55.27 utc:2391: update_nvt_cache_retry: rebuild successful
Problem is that now it stucked (see screenshot), does nothing (CPU and disk are not in use) and I still cannot connect to it with
Why? What should I do now? Restart?
I tried to run the "docker run" command shown in the documentation, but the container did not start with the following errors:
`
Unable to find image 'immauss/openvas:latest' locally
Trying to pull repository registry.access.redhat.com/immauss/openvas ...
Pulling repository registry.access.redhat.com/immauss/openvas
Trying to pull repository registry.redhat.io/immauss/openvas ...
Trying to pull repository docker.io/immauss/openvas ...
latest: Pulling from docker.io/immauss/openvas
83ee3a23efb7: Pull complete
db98fc6f11f0: Pull complete
f611acd52c6c: Pull complete
dc16d3b591b7: Pull complete
ec379549505f: Pull complete
047a862b2705: Pull complete
60960b44262f: Pull complete
f12e12d18794: Pull complete
Digest: sha256:f57903eb437a45fdbfb9b9646a2d0235196cf10d9e0ef2f71d1108e828c08be5
Status: Downloaded newer image for docker.io/immauss/openvas:latest
9:C 23 Mar 2021 15:21:11.243 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
9:C 23 Mar 2021 15:21:11.243 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=9, just started
9:C 23 Mar 2021 15:21:11.243 # Configuration loaded
Wait for redis socket to be created...
Testing redis status...
Redis ready.
Creating Data and database folder...
mv: cannot remove '/var/lib/postgresql/12/main/base/1/112': No such file or directory
mv: cannot remove '/var/lib/postgresql/12/main/base/1/113': No such file or directory
mv: cannot remove '/var/lib/postgresql/12/main/base/1/1247': No such file or directory
mv: cannot remove '/var/lib/postgresql/12/main/base/1/1247_fsm': No such file or directory
mv: cannot remove '/var/lib/postgresql/12/main/base/1/1247_vm': No such file or directory
...
`
What I did wrong?
Tks.
Marco Aurélio
I have been running increasing bigger scans, and run into this occasionally. There is a formula for the number of Redis DBs that should be configured:
You need at least
one db for the main data
one db for the nvt cache
one db for every scan
one db for every target host of a scan
So it is 2 + n * m dbs where n is the number of concurrent scans and m the number of hosts per scan.
However, the start.sh script sets this at 128. Can this be a configurable number through an environment variable, and probably make it a larger number than 128?
I haven't got to create a pull request yet, but putting it here in case you get to it before I do.
docker run --detach --publish 8080:9392 -e PASSWORD="admin" --name openvas immauss/openvas:20.08.03.1
container doesn't start
docker logs openvas
8:C 25 Jan 2021 15:37:40.415 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
8:C 25 Jan 2021 15:37:40.415 # Redis version=5.0.7, bits=64, commit=00000000, modified=0, pid=8, just started
8:C 25 Jan 2021 15:37:40.415 # Configuration loaded
Wait for redis socket to be created...
Testing redis status...
Redis ready.
Creating Data and database folder...
mv: cannot move '/var/lib/postgresql/12/main' to '/data/database': No such file or directory
tryed also openvas:20.08.03 and openvas:20.08.02 - same error
centos 7
docker 1.12
Hi, everybody..
I have executed:
docker run -d -p 9392:9392 -p 9390:9390 -e GMP=9390 --name openvas -v /var/openvas:/data --name openvas immauss/openvas:latest
but, I've got:
status: Downloaded newer image for immauss/openvas:latest
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm/v7) and no specific platform was requested
root@odroid:~# uname -a
Linux odroid 4.14.180-178 #1 SMP PREEMPT Wed Sep 2 12:39:45 -03 2020 armv7l armv7l armv7l GNU/Linux
root@odroid:~# docker version
Client: Docker Engine - Community
Version: 20.10.6
API version: 1.41
Go version: go1.13.15
Git commit: 370c289
Built: Fri Apr 9 22:47:33 2021
OS/Arch: linux/arm
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.6
API version: 1.41 (minimum version 1.12)
Go version: go1.13.15
Git commit: 8728dd2
Built: Fri Apr 9 22:45:33 2021
OS/Arch: linux/arm
Experimental: false
containerd:
Version: 1.4.6
GitCommit: d71fcd7d8303cbf684402823e425e9dd2e99285d
runc:
Version: 1.0.0-rc95
GitCommit: b9ee9c6314599f1b4a7f497e1f1f856fe433d3b7
docker-init:
Version: 0.19.0
GitCommit: de40ad0
thanks in advance.
I just redeployed the docker container today and got this message after starting the first scan.
Summary
ATTENTION:
Your vulnerability tests are out of maintenance and not updated since September 1st 2020. Your setup of Greenbone Source Edition will not report about any new threats in your scanned environment since this date!
REASON:
Your Greenbone setup is connected to a discontinued download server of the Greenbone Community Feed. The Greenbone Community Feed is still available via a new download server. The discontinuation announcement was posted on May 13th at the Greenbone Community Portal.
SOLUTION:
You can consider to upgrade your setup to a Greenbone enterprise product which also provides you the full scan coverage via Greenbone Security Feed (see PROFESSIONAL SOLUTION). Alternatively you can continue with the Greenbone Community Feed (see FREE COMMUNITY SOLUTION).
Is there a way to fix that?
Using latest version (as of today 2020-10-31) with compose
openvas:
container_name: openvas
environment:
- PASSWORD=xxx
- RELAYHOST=xxx.com
#hostname: openvas.${hostname}
image: immauss/openvas
labels:
- com.centurylinklabs.watchtower.enable=true
ports:
- 8083:9392
restart: always
volumes:
- /etc/timezone:/etc/timezone:ro
- /etc/localtime:/etc/localtime:ro
- /opt/docker/openvas:/data
container restarts with error message from the logs:
Setup / Fix the /usr/local/var/run
10:C 31 Oct 12:16:16.494 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
10:C 31 Oct 12:16:16.494 # Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=10, just started
10:C 31 Oct 12:16:16.494 # Configuration loaded
Wait for redis socket to be created...
Testing redis status...
Redis ready.
Starting PostgreSQL...
Removed stale pid file.
Fixing sync script options ...
Updating NVTs...
<28>Oct 31 12:16:19 greenbone-nvt-sync: The log facility is not working as expected. All messages will be written to the standard error stream.
<28>Oct 31 12:16:19 greenbone-nvt-sync: Another process related to the feed update is already running.
any ideas?
The current Docker health check implementation fails when using HTTPS=true, this is due to checking against "http://" instead of "https://"
Proposed solution:
How can we use this with our own SSL certificate? is there an var we can pass into docker with the locations of our certificate files?
Hi,
First thing to say, thank you for providing an up2date version of OpenVAS!
Question: My mail alerts aren't working, probably caused by some security settings of my mail server. Is it possible to get the mail logs from Postfix? I can't find anything inside the container since syslog isn't available. Logging to a file seems possible with Postfix >3.4 but included is a 3.3 version...
any ideas?
If you are trying to get the latest version to run and having issues, fear not, I'm working on it.
Check back here for the latest.
-Scott
Using latest tag I'm receiving a startup error since today:
DETAIL: The data directory was initialized by PostgreSQL version 12, which is not compatible with this version 11.11 (Ubuntu 11.11-1.pgdg20.04+1)
Was there a downgrade (seems so) but why?
Line 172 in facbd0d
/var/run -> /run
/usr/local/var/run -> /run
The symlink is causing an error
gsad gmp:WARNING:2020-09-15 11h38.30 utc:555: Failed to connect to server at /usr/local/var/run/gvmd.sock: Too many levels of symbolic links
gsad gmp:WARNING:2020-09-15 11h38.30 utc:555: Authentication failure for 'admin' from 172.16.12.102. Status was 1.
As the various run dirs are pointing back to /run anyway the whole stanza should be removable, no?
Hi,
Is it normal, that feed version from https://community.greenbone.net/ stucked at 202104060959 ? Also, is it sufficient to restart the docker image for the nvt upgrades, or new image pull is a must?
Thanks,
Istvan
Hi !
I do have issues with the latest image.
compose file
version: "3.3"
services:
openvas:
ports:
- "808:9392"
environment:
- "PASSWORD=paswd"
dns:
- 1.1.1.1
volumes:
- "openvas:/data"
container_name: openvas
image: immauss/openvas:latest
volumes:
openvas:
log
penvas | Unpacking base feeds data from /usr/lib/var-lib.tar.xz
openvas | Migrating the database to the latest version if needed.
openvas | Updating NVTs and other data
openvas | This could take a while if you are not using persistent storage for your NVTs
openvas | or this is the first time pulling to your persistent storage.
openvas | the time will be mostly dependent on your available bandwidth.
openvas | We sleep for 5 seconds between sync command to make sure everything closes
openvas | and it doesnt' look like we are connecting more than once.
openvas | Pulling NVTs from greenbone
openvas | <28>May 5 15:29:11 greenbone-nvt-sync: The log facility is not working as expected. All messages will be written to the standard error stream.
openvas | <29>May 5 15:29:11 greenbone-nvt-sync: No Greenbone Security Feed access key found, falling back to Greenbone Community Feed
openvas | <29>May 5 15:29:16 greenbone-nvt-sync: Configured NVT rsync feed: rsync://feed.community.greenbone.net:/nvt-feed
openvas | rsync: failed to connect to feed.community.greenbone.net (45.135.106.142): Connection timed out (110)
openvas | rsync: failed to connect to feed.community.greenbone.net (2a0e:6b40:20:106:20c:29ff:fe67:cbb5): Network is unreachable (101)
openvas | rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3]
openvas | <27>May 5 15:31:24 greenbone-nvt-sync: rsync failed.
openvas | Pulling scapdata from greenbone
openvas | rsync: failed to connect to feed.community.greenbone.net (45.135.106.142): Connection timed out (110)
openvas | rsync: failed to connect to feed.community.greenbone.net (2a0e:6b40:20:106:20c:29ff:fe67:cbb5): Network is unreachable (101)
openvas | rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3]
openvas exited with code 1
tried also to give it a public DNS but it was anyways resolved but nothing retrieved
Image: immauss/openvas:armv7
Version: 21.04.02
Just tried this on my raspberrypi 3 and had some problems :)
First, I had to recreate the container with "Privileged mode" on, as I got this error:
sleep: cannot read realtime clock: Operation not permitted
Second, after that was fixed, I got the following error:
10 Jul 2021 23:40:13.554 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
10 Jul 2021 23:40:13.554 # Redis version=5.0.7, bits=32, commit=00000000, modified=0, pid=9, just started
10 Jul 2021 23:40:13.554 # Configuration loaded
Wait for redis socket to be created...
Testing redis status...
Redis ready.
Creating Data and database folder...
Fixing Database folder...
Fixing local/var/lib ...
cp: cannot stat '/usr/local/var/lib/*': No such file or directory
The following folders were created on the storage:
Using latest amd64 tag from docker hub with a clean data path (from scratch)
sha256:34cc22d839eb28798681285a25c2eb0f1b7c955779c8c0154c7fd68a97a52454
openvas:
container_name: openvas
cpus: 4
environment:
- PASSWORD=${openvas_OV_PASSWORD}
- RELAYHOST=${EMAIL_HOST} # immauss/openvas, securecompliance/gvm
- SMTPPORT=25 # immauss/openvas, securecompliance/gvm
- QUIET=true # immauss/openvas
- SKIPSYNC=true
hostname: openvas.${HOSTNAME}
image: immauss/openvas
labels:
- ${WATCHTOWER_TRUE}
- diun.enable=true
- diun.watch_repo=true
- traefik.enable=true
- "traefik.http.routers.openvas.rule=Host(`openvas.${HOSTNAME}`)"
- traefik.http.routers.openvas.entrypoints=web-secure
- traefik.http.routers.openvas.tls.certresolver=le
- traefik.http.routers.openvas.tls=true
- traefik.http.routers.openvas.priority=2
- traefik.http.routers.openvas.tls.options=default
- traefik.http.routers.openvas.service=openvas
- traefik.http.services.openvas.loadbalancer.server.port=9392
networks:
- web
restart: always
volumes:
- ${DOCKER_PATH}/openvas:/data # immauss/openvas, securecompliance/gvm
seeing a WARNING message every 10 seconds:
md manage:WARNING:2021-05-31 20h21.33 utc:32750: secinfo_feed_version_status: last scap database update later than last feed update
pdf report not working, download ends with a 0 byte file (correct file name but no content); doesn't work as email report
It would be nice to be able to configure the session timeout.
It should be a gsad parameter at launch (--timeout)
While writing analysis having to re-login dozen of times on that wacky interface is really a PITA.
Thanks
First of all thank you for the quick solution in the last days, it seems that this is working again now! 👍
Unfortunately, there now seem to be some problems with logging:
2020-09-14 12:15:00 | stdout | Updating NVTs...
2020-09-14 12:15:00 | stdout | <28>Sep 14 12:15:00 greenbone-nvt-sync: The log facility is not working as expected. All messages will be written to the standard error stream.
2020-09-14 12:15:00 | stdout | touch: cannot touch '/usr/local/var/run/feed-update.lock': Permission denied
2020-09-14 12:15:00 | stdout | <29>Sep 14 12:15:00 greenbone-nvt-sync: No Greenbone Security Feed access key found, falling back to Greenbone Community Feed
2020-09-14 12:15:00 | stdout | <29>Sep 14 12:15:00 greenbone-nvt-sync: Configured NVT rsync feed: rsync://feed.community.greenbone.net:/nvt-feed
The log file is now completely spammed with the download massages for each file :)
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.