-
Notifications
You must be signed in to change notification settings - Fork 883
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
CVEs found #1784
Comments
I decided to give it a go and created a PR: I hope thats to you liking. :-) |
We will attempt the changes needed in notification-engine to fix the |
Thank you! I had a closer look at CVE-2020-8554 and that's not currently resolvable by updates but needs an admission webhook. At least it's out of argo-rollouts hands and can be ignored. This is what I get by running trivy for golang:
Looking at GMS-2021-101 it seems to require another update to the k8s api: github.com/argoproj/argo-rollouts However, the information that I could find suggests it's a documentation issue and could propably be ignored. |
Once the low hanging CVE fruits are handled, would it be possible to to a release? That way I could make a PR to stakater/reloader which for me what this was all about. |
@smuda we will be having new release next week. Changes will be part of it. |
Does this release include CVE-2020-8554? If not is there an update for that fix? |
it is part of 1.2.0-rc1 |
Summary
When scanning for vulns there are a number of CVEs:
I'd be happy to create one or more PRs for those CVE's that are fixable by simply upgrading the dependencies but it seems there are a lot of changes required.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: