Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows

Why it is Yellow

• CVSS 6.1 medium

References

• https://github.com/kubeflow/pipelines/commit/fedc25e3f7251933d4a37b964bc3e8176beea28e
• https://github.com/kubeflow/pipelines/pull/12295
• https://github.com/kubeflow/pipelines/releases/tag/2.15.0
• https://github.com/kubeflow/pipelines/security/advisories/GHSA-g3qx-frcg-j979

Original description

Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.15.0, the frontend routes /pipeline/k8s/pod and /pipeline/k8s/pod/events use frontend/server/k8s-helper.ts to include untrusted podname and podnamespace query values and backend error details in HTML-capable error responses. An unauthenticated attacker can craft a link that executes JavaScript in the frontend origin when a user who satisfies the deployment's authentication and route-access requirements follows it and reaches an affected response. Cookie disclosure depends on cookie attributes, and server-side code execution or availability impact is not established. This issue is fixed in version 2.15.0.