Kubeflow Pipelines: Unauthenticated SSRF through artifact provider endpoints

Summary

Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the frontend artifact download path for source=s3 or source=minio accepts providerInfo.Params.endpoint, and the archived pod-log path accepts S3-compatible endpoint metadata from workflow status, without requiring those endpoints to match operator-controlled storage configuration. In the shipped authorization-disabled standalone configuration, an unauthenticated caller can make the shared ml-pipeline-ui pod connect to arbitrary reachable hosts and return response data; requests may also reveal an access-key identifier when signed with configured object-store credentials. Multi-user secret-backed metadata remains restricted to the server namespace. This issue is fixed in version 2.18.0.

Remediation

1. Inventory every kubeflow pipelines deployment, including staging.
2. No fixed version appears in the public sources yet. Check the references below and the vendor directly.

References

• Referencehttps://github.com/kubeflow/pipelines/security/advisories/GHSA-3pcj-8j5w-jmxq
• Referencehttps://github.com/kubeflow/pipelines/pull/14349
• Referencehttps://github.com/kubeflow/pipelines/commit/0b77f9b07bfb9860dc90106003bbc3e2fe0e0965
• Referencehttps://github.com/kubeflow/pipelines/releases/tag/2.18.0