GHSA-prqf-xr2j-xf65
Potential privilege escalation on Kubernetes >= v1.19 when the Argo Sever is run with `--auth-mode=client`
Quick fix
GHSA-prqf-xr2j-xf65 — github.com/argoproj/argo-workflows/v3: upgrade to the fixed version with the command below.
go get github.com/argoproj/argo-workflows/v3@v3.0.9Details
### Impact
This is pro-active fix. No know exploits exist.
Impacted:
* You're running Kubernetes >= v1.19 * You're running Argo Server * It is configured to with `--auth-mode=client` * Is not configured with `--auth-mode=server` * You are not running Argo Server in Kubernetes pod. E.g. on bare metal or other VM. * You're using client key to authenticate on the server. * The server has more permissions that the connecting client's account.
The client's authentication will be ignored and the server's authentication will be used. This will result in privilege escalation to that of the the server's account.
### Patches
https://github.com/argoproj/argo-workflows/pull/6506
### Workarounds
None.
Are you affected?
Enter the version of the package you're using.
Affected packages
3.0.0Fixed in: 3.0.9go get github.com/argoproj/argo-workflows/v3@v3.0.93.1.0Fixed in: 3.1.6go get github.com/argoproj/argo-workflows/v3@v3.1.6