-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
container Image vulnerabilities #232
Comments
@rjrhaverkamp Please rebuild your image to use the latest version of As an NGINX Plus customer you can get support directly from us. If you prefer, you can create a support ticket, using the email addresses (for you and for NGINX engineering) in your support contract to send and receive support case information. |
Hi @pleshakov All vulnerabilities that have a patch available are now fixed. There are still 3 critical in severity and 13 high found, but according to the scanner these don't have a patch available. Thanks! |
Another option would be to move to a slimmer version of a base distro - e.g. debian:stretch-slim - which hopefully will have less of an attack surface. Also removing everything install during the build of the image is a good idea to minimize that issue as well. Unfortunately there is no good way other than rebuilding an image every once in a while. |
@rjrhaverkamp please check https://github.com/nginxinc/kubernetes-ingress/blob/plus-dockerfiles/nginx-controller/DockerfileForPlusStretch for a DockerFile for |
I wonder if that image scanner takes into account actual patches in the debian packages - and not only the versions.. But indeed, it looks miles better. |
the image for Plus now uses Debian Stretch -- 0dafb34 |
Hi @pleshakov
we make use of multiple NGINX plus instances in google kubernetes engine. Google recently added a vulnerability scanner to its image registry.
As you can see in the image below it detected 93 vulnerabilities of which 6 Critical, 19 High, 50 Medium, 6 Low and 12 Unknown in severity.
I'm not sure if this affects the running NGINX process at all, but I think this should be fixed.
If I can be of any assistance, let me know.
~ Rob
The text was updated successfully, but these errors were encountered: