Repository files navigation

exploit-db-server combinesgo-exploitdb running inserver mode with a mechanism for periodically updating the known exploits intoa single container which can be deployed standalone or on kubernetes.

It will update the database (from all supported sources) once when thecontainer starts and then every 3 hours until the container stops.

• Building
• Running
• Querying
• Contributing
• Code of Conduct
• License

# Registry defaults to ghcr.io/openclarity and tag defaults to the latest commit IDDOCKER_REGISTRY=<registry> DOCKER_TAG=<tag> make docker

docker run -d -p 1326:1326 --name exploit-db-server <registry>/exploit-db-server:<tag>

To persist the database between container runs:

mkdir /opt/exploit-dbdocker run -d -p 1326:1326 -v /opt/exploit-db:/var/lib/go-exploitdb -name exploit-db-server <registry>/exploit-db-server:<tag>

Example for how to query the server are given on thego-exploitdb README:

• Search Exploits by CVE ID
• Search Exploits by Unique ID

If you are ready to jump in and test, add code, or help with documentation,please follow the instructions on ourcontributing guidefor details on how to open issues, setup VMClarity for development and test.

You can view our code of conducthere.

Apache License, Version 2.0