You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps did you take and what happened:
When we scanned kubeflow docker images v1.9.0, we found following vulnerabilities
During a security scan of the Kubeflow Docker images Kubeflow release version 1.9.0, we identified several vulnerabilities. Below are the details of the affected Docker images and their corresponding CVEs:
I have investigated some of the CVEs, and they can all be resolved by updating the dependencies.
I have only found boards for posting issues for individual components. Since the CVEs affect multiple components, I have reported the bug here for now. If necessary, I can create multiple issues.
The text was updated successfully, but these errors were encountered:
Thank you for rising this @StefanSorensen! @juliusvonkohout@akgraner Do we have any guidelines from the security perspective on how these CVEs should be addressed ?
cc @kubeflow/kubeflow-steering-committee
First of all we have the scans as well on every commit. For example https://github.com/kubeflow/manifests/actions/runs/11073006658/job/30768570843 So it is already public. I also pointed @StefanSorensen on slack to the script to upgrade istio from 1.22.1 to 1.22.x and the kserve repository. Most others issues here are from kubeflow/dashboard / kubeflow/kubeflow, kubeflow/pipelines or out of scope (rancher). In the end we just want people to raise PRs for such public stuff.
/kind bug
What steps did you take and what happened:
When we scanned kubeflow docker images v1.9.0, we found following vulnerabilities
During a security scan of the Kubeflow Docker images Kubeflow release version 1.9.0, we identified several vulnerabilities. Below are the details of the affected Docker images and their corresponding CVEs:
I have investigated some of the CVEs, and they can all be resolved by updating the dependencies.
I have only found boards for posting issues for individual components. Since the CVEs affect multiple components, I have reported the bug here for now. If necessary, I can create multiple issues.
The text was updated successfully, but these errors were encountered: