Kubeflow Model Registry through 0.3.17 contains a server-side request forgery vulnerability that allows namespace users to steal the controller ServiceAccount token via the modelregistry.kubeflow.org/url annotation. Attackers can create an InferenceService pointing the annotation at their server, capture the bearer token, and modify other tenants' InferenceServices cluster-wide.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
Low
Partial data leak
Integrity
High
Complete data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
References 6
https://github.com/kubeflow/hub
disclosure@vulncheck.com
https://github.com/kubeflow/hub/blob/v0.3.17/cmd/controller/main.go#L224-L228
disclosure@vulncheck.com
https://github.com/kubeflow/hub/blob/v0.3.17/pkg/inferenceservice-controller/co…
disclosure@vulncheck.com
https://github.com/kubeflow/hub/blob/v0.3.17/pkg/openapi/client.go#L420-L423
disclosure@vulncheck.com
https://hackmd.io/@1ExmmukzRMWN7B4gQ4W-4Q/kubeflow-hub-controller-token-url-for…
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/kubeflow-model-registry-through-0.3.17-ssr…
disclosure@vulncheck.com