Skip to content
OpenAdvisories
Low GHSA-prqf-xr2j-xf65 GO-2022-0405

Potential privilege escalation on Kubernetes >= v1.19 when the Argo Sever is run with `--auth-mode=client`

Published Aug 23, 2021 · Updated Aug 21, 2024 · Assigned by GHSA

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=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.

Affected packages

EcosystemPackageAffectedFixedRecord
Go github.com/argoproj/argo-workflows all versions — GO-2022-0405
Go github.com/argoproj/argo-workflows/v2 all versions — GO-2022-0405
Go github.com/argoproj/argo-workflows/v3 >= 3.0.0, < 3.0.9 3.0.9 GHSA-prqf-xr2j-xf65
Go github.com/argoproj/argo-workflows/v3 >= 3.1.0, < 3.1.6 3.1.6 GHSA-prqf-xr2j-xf65
Go github.com/argoproj/argo-workflows/v3 >= 3.0.0, < 3.0.9 · >= 3.1.0, < 3.1.6 3.0.9, 3.1.6 GO-2022-0405

References