Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-prqf-xr2j-xf65
No affected components available
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.
Measures severity based on intrinsic characteristics of the vulnerability, independent of environment.
No exploitation activity has been observed at this time. Continue routine monitoring.
Probability that this vulnerability will be exploited in the wild within the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard