Privilege Escalation Affecting github.com/argoproj/argo-workflows/v3/util/kubeconfig Open this link in a new tab package, versions >=3.1.0 <3.1.6 >=3.0.0 <3.0.9
Exploit Maturity
Proof of concept
Attack Complexity
High
Privileges Required
High
Scope
Changed
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications-
snyk-id
SNYK-GOLANG-GITHUBCOMARGOPROJARGOWORKFLOWSV3UTILKUBECONFIG-1569195
-
published
24 Aug 2021
-
disclosed
23 Aug 2021
-
credit
Unknown
Introduced: 23 Aug 2021
CWE-264 Open this link in a new tabHow to fix?
Upgrade github.com/argoproj/argo-workflows/v3/util/kubeconfig
to version 3.1.6, 3.0.9 or higher.
Overview
github.com/argoproj/argo-workflows/v3/util/kubeconfig is a Workflow engine for Kubernetes
Affected versions of this package are vulnerable to Privilege Escalation. Potential privilege escalation when the Argo Sever is run with --auth-mode=client
. This is a pro-active fix. No know exploits exist. You are impacted if:
- You're running Kubernetes grater than or equal to
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.