-
Notifications
You must be signed in to change notification settings - Fork 290
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
k3d/5.6.0-r9: cve remediation #16427
Conversation
These CVE's are not present in the ain k3d package it is in the k3d-proxy and it come from |
K3d was using a fork of kelseyhightower/confd with almost no code update, just go version update with go.mod file that is not present in the original repo last relese. Now using this as deps are way more updated there compare to the forkes one k3d is using Signed-off-by: Debasish Biswas <debasishbsws.dev@gmail.com>
Package k3d: Click to expand/collapsePackage k3d: Package k3d-tools: Click to expand/collapsePackage k3d-tools: Package k3d-proxy: Click to expand/collapsePackage k3d-proxy: bincapz found differences: Click to expand/collapseChanged: k3d-proxy/usr/bin/confdPrevious Risk: 🚨 4/CRITICAL
|
K3d was using a fork of As there are a lot of CVE in the forked confd k3d is using compared to the original confd that has been updated with new dependencies it is better to use that one. ISSUE is that the latest release was in 2018 May. And the changes are recent. I avoid git-checkout to the last tag and instead use simple git commands in the runs statement. It fixes all the CVE's but not sure if there Is any better way. |
k3d/5.6.0-r9: fix GHSA-6q6q-88xp-6f2r/GHSA-ppp9-7jff-5vj2/GHSA-8c26-wmh5-6g9v/GHSA-j2rp-gmqv-frhv/GHSA-m425-mq94-257g/GHSA-c3h9-896r-86jm/GHSA-7f33-f4f5-xwgw/GHSA-vvpx-j8f3-3w6h/GHSA-m69r-9g56-7mv8/
Advisory data: https://github.com/wolfi-dev/advisories/blob/main/k3d.advisories.yaml