Kubeflow pipelines
Kubeflow: Unauthenticated path traversal to arbitrary file read on ml-pipeline-ui via the volume artifact source
Kubeflow Pipelines enables users to build and deploy portable, scalable machine learning workflows. Prior to 2.18.0, the volume artifact handler for GET /artifacts/get?source=volume did not confine a caller-supplied file path to the selected volume. A caller who can reach the route and identify an existing mounted volume can use path traversal to read files outside that volume when the artifact-serving process can read them. The frontend pod serves the request when artifact proxying is disabled, while the selected namespace's artifact-service pod serves it when proxying is enabled. A deployment with authentication disabled requires no application credentials; in multi-user deployments, the caller ordinarily must be authorized for the supplied namespace. This issue is fixed in version 2.18.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.18.0
Fixed in 2.18.0
Mitigation
Upgrade pipelines to 2.18.0 or later.
References
- Vendor advisory github.com/kubeflow/pipelines/security/advisor…
- Patch github.com/kubeflow/pipelines/pull/13677
- Patch github.com/kubeflow/pipelines/commit/4d9bc5ab1…
1 more
- Release notes github.com/kubeflow/pipelines/releases/tag/2.1…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.