Skip to content
Fencer Intel
low —

GHSA-prqf-xr2j-xf65 json

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

published 5y ago modified 8mo ago also GO-2022-0405

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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

Patch / fix

  • go github.com/argoproj/argo-workflows/v3 3.0.9, 3.1.6

Is GHSA-prqf-xr2j-xf65 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
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 github.com/argoproj/argo-workflows
all versions
 no fix listed
go github.com/argoproj/argo-workflows/v2
all versions
 no fix listed

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.