Affected versions
Version ranges need review.
- Affected versions
- *
- Fixed version
- Not reported
- Affected versions
- >= 3.1.0, < 3.1.6
- Fixed version
- 3.1.6
- Affected versions
- >=3.0.0 <3.0.9 || >=3.1.0 <3.1.6
- Fixed version
- 3.0.9 · 3.1.6
- Affected versions
- >= 3.0.0, < 3.0.9
- Fixed version
- 3.0.9
- Affected versions
- *
- Fixed version
- Not reported
Description
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=clientIs not configured with
--auth-mode=serverYou 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.

