-
Notifications
You must be signed in to change notification settings - Fork 47
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
Address critical vulnerabilities #218
Comments
hawksight
added a commit
to hawksight/kubestr
that referenced
this issue
Jan 31, 2024
- Builder image moved to go 1.21 as per go.mod - Runtime image upgraded to alpine 3.19 Hopfully fixes kastenhq#218. Signed-off-by: Peter Fiddes <[email protected]>
julio-lopez
pushed a commit
that referenced
this issue
Feb 1, 2024
- Builder image moved to go 1.21 as per go.mod - Runtime image upgraded to alpine 3.19 Hopfully fixes #218. Signed-off-by: Peter Fiddes <[email protected]>
TY @julio-lopez for reviewing and closing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey thanks for the project. I was just checking out the latest image v0.4.41 which is now about 6 months ago and noticed a few vulnerabilities. I think they are probably addressable with a new build / image update as most of them seem to be in the base image.
Here's a trivy output for reference:
All the critical vulnerabilities look like they have fixes.
Having these fixed makes it easier to run in more secure environments as often the barrier to entry is no critical vulns, or atleast none that have fixes.
I'm happy to have a go at fixing this if you can point me to some guidance on building the project. (Similar question to #217 ).
The text was updated successfully, but these errors were encountered: