Advisory

GHSA-prqf-xr2j-xf65

Also known as: GO-2022-0405

Summary

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

Details

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2021-08-23 19:41 UTC
Modified
2024-08-21 14:57 UTC

Affected packages and fixes

github.com/argoproj/argo-workflows/v3

Go · All systems

Affected

  • introduced 3.0.0, fixed 3.0.9 (semver)

Fixed versions

3.0.9

Fix

github.com/argoproj/argo-workflows/v3

Go · All systems

Affected

  • introduced 3.1.0, fixed 3.1.6 (semver)

Fixed versions

3.1.6

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences