Argo CD improper access control bug can allow malicious user to escalate privileges to admin level
Date: 2022-07
Affected: go/github.com/argoproj/argo-cd/v2, go/github.com/argoproj/argo-cd/v2, go/github.com/argoproj/argo-cd/v2
Attack vector: auth-bypass
Category: vulnerability-disclosure
Severity: Critical
CVE: CVE-2022-1025
CVE-2022-24768
CWE: CWE-1220
CWE-200
CWE-269
CWE-284
CWE-862
CWE-863
CVSS: 8.8 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H)

# Impact ## Impacts for versions starting with v1.0.0 All unpatched versions of Argo CD starting with v1.0.0 are vulnerable to an improper access control bug, allowing a malicious user to potentially escalate their privileges to admin-level. To perform the following exploits, an authorized Argo CD user must have push access to an Application's source git or Helm repository or `sync` and `override` access to an Application. Once a user has that access, different exploitation levels are possible depending on their other RBAC privileges: 1. If that user has `update` access to the Application, they can modify any resource on the Application's destination cluster. If the destination cluster is or can be made to be the same as the cluster hosting Argo CD, the user can escalate their Argo CD permissions to admin-level. 2. If the user has `delete` access to the Application, they can delete any resource on the Application's destination cluster. (This exploit is possible starting with v0.8.0.) 3. If the user has `get` access to the Application, they can view any resource on the Application's destination cluster (except for the contents of Secrets) and list [actions](https://argo-cd.readthedocs.io/en/stable/operator-manual/resource_actions/) available for that resource. 4. If the user has `get` access to the Application, they can view the logs of any Pods on the Application's destination cluster. 5. If the user has `action/{some action or *}` access on the Application, they can run a


Mitigations:

Architectural layers (MAESTRO):