Ljyanesm

Name of the Vulnerable Software and Affected Versions: Argo Workflows versions 3.5.7 through 3.5.8 Description: Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. When using `--auth-mode=client`, archived workflows can be retrieved with a fake or spoofed token via the GET Workflow endpoint: `/api/v1/workflows/{namespace}/{name}`. No authentication is performed by the server itself on `client` tokens. Authentication and authorization are instead delegated to the k8s API server. However, the workflow archive does not interact with k8s, and so any token that looks valid will be considered authenticated. To handle the lack of pass-through k8s authN/authZ, the workflow archive specifically does the equivalent of a `kubectl auth can-i` check for respective methods. In versions 3.5.7 and 3.5.8, the auth check was accidentally removed on the GET Workflow endpoint's fallback to archived workflows, allowing archived workflows to be retrieved with a fake token. Recommendations: For Argo Workflows versions 3.5.7 and 3.5.8, update to version 3.6.2 or 3.5.13 to fix the vulnerability. As a temporary workaround, consider disabling the `--auth-mode=client` mode until a patch is available. Restrict access to the `/api/v1/workflows/{namespace}/{name}` endpoint to minimize the risk of exploitation. Avoid using fake or spoofed tokens in the `Authorization` header until the issue is resolved.