-
Notifications
You must be signed in to change notification settings - Fork 183
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
CVE-2023-4863 in nginx-unprivileged image #3365
Comments
list of vulnerabilities
|
Hi Rajendra, thanks for creating the issue. Are you sure the scan was performed correctly? For Helm Chart sumologic-kubernetes-collection/deploy/helm/sumologic/values.yaml Lines 614 to 617 in 6bf9b71
|
I can corroborate what Rajendra is saying but also add some details as the problem is also in the updated 1.25.2 version. It seems that public.ecr.aws/sumologic/nginx-unprivileged:1.25.2-alpine also has the newer CVE-2023-4863 / libwebp issue. A Prisma scan shows this: Image public.ecr.aws/sumologic/nginx-unprivileged:1.25.2-alpine Type | Highest severity | Description I also just did a trivy scan. public.ecr.aws/sumologic/nginx-unprivileged:1.25.2-alpine (alpine 3.18.3) I don't have an AWS ECR scan handy yet. |
It looks like the issues in Alpine were patched in https://alpinelinux.org/posts/Alpine-3.18.4-released.html main/libwebp: upgrade to 1.3.2 Thanks for looking into this! |
Did some more digging. public.ecr.aws/nginx/nginx-unprivileged:1.25-alpine3.18 (alpine 3.18.4) Total: 1 (HIGH: 1, CRITICAL: 0) There are other fixes on the way, but they might be delayed: It looks like it might take a few days+ to work out the latest changes. Might it be worthwhile to put in a PR for tag: |
Hey, thank you both for the detailed investigation! I think we should just upgrade to whatever is available, since we wanted to issue new releases this week anyway. Once nginx gets 1.25.3 out, we can upgrade to that one separately. One somewhat annoying thing about the nginx-unprivileged repository is that most (all?) of the tags move. What I ended up doing is simply rehosting the current |
Thanks for your help on this!!! |
Released 3.17.0 and 4.1.0 containing this fixe earlier today. |
The latest nginx-unprivileged:1.23.3-alpine
image version for the sumologic-kubernetes-collection chart (chart version 3.16.2, nginx-unprivileged image version public.ecr.aws/sumologic/nginx-unprivileged:1.23.3-alpine
), has 1 critical vulnerability and 9 high vulnerabilities, found by aws ecr vulnerability scans. We are currently working to drive both of these categories to 0 in images running in our kubernetes cluster. Is there a time line where we can expect these to be addressed in your image? And does sumo have a plan to keep these categories at 0 (or as close as possible as new issues are found) going forward?
The text was updated successfully, but these errors were encountered: