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

Why it is Yellow

• CVSS 8.6 high
• Remotely exploitable without logging in

References

• https://github.com/kubeflow/pipelines/commit/4d9bc5ab12b67efedb3923ef428a399cb445cf5f
• https://github.com/kubeflow/pipelines/pull/13677
• https://github.com/kubeflow/pipelines/releases/tag/2.18.0
• https://github.com/kubeflow/pipelines/security/advisories/GHSA-v3vh-xv5f-p4p4

Original description

Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the frontend GET /artifacts/get route accepts source=http or source=https with caller-controlled bucket and key values, and isAllowedResourceName permits an all-digit decimal host that the URL parser converts to an IPv4 address. The default ALLOWED_ARTIFACT_DOMAIN_REGEX and authorization-disabled standalone configuration allow an unauthenticated caller to fetch internal HTTP resources and receive their response body. In the authenticated multi-user configuration, the same destination-validation defect is reachable by a low-privilege tenant with a valid identity and authorized namespace. Cloud credential disclosure depends on reachable metadata services and attached roles, and the issue does not establish IMDSv2 bypass or credential access when metadata is blocked. This issue is fixed in version 2.18.0.