First published: Wed Mar 23 2022(Updated: )
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All unpatched versions of Argo CD starting with 1.0.0 are vulnerable to an improper access control bug, allowing a malicious user to potentially escalate their privileges to admin-level. Versions starting with 0.8.0 and 0.5.0 contain limited versions of this issue. To perform 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. A patch for this vulnerability has been released in Argo CD versions 2.3.2, 2.2.8, and 2.1.14. Some mitigation measures are available but do not serve as a substitute for upgrading. To avoid privilege escalation, limit who has push access to Application source repositories or `sync` + `override` access to Applications; and limit which repositories are available in projects where users have `update` access to Applications. To avoid unauthorized resource inspection/tampering, limit who has `delete`, `get`, or `action` access to Applications.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Linuxfoundation Argo-cd | >=0.5.0<2.1.14 | |
Linuxfoundation Argo-cd | >=2.2.0<2.2.8 | |
Linuxfoundation Argo-cd | >=2.3.0<2.3.2 | |
Argoproj Argo Cd | >=0.5.0<2.1.14 | |
Argoproj Argo Cd | >=2.2.0<2.2.8 | |
Argoproj Argo Cd | >=2.3.0<2.3.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-24768 is a vulnerability in Argo CD, a declarative GitOps continuous delivery tool for Kubernetes, that allows a malicious user to potentially escalate their privileges to admin-level.
The severity of CVE-2022-24768 is critical, with a severity value of 8.8.
All unpatched versions of Argo CD starting from 1.0.0 up to version 2.3.2 are affected by CVE-2022-24768.
To fix CVE-2022-24768, you should update Argo CD to version 2.3.2 or apply the necessary patches provided by the vendor.
Yes, you can find additional information about CVE-2022-24768 in the references provided: [Reference 1](https://github.com/argoproj/argo-cd/commit/af03b291d4b7e9d3ce9a6580ae9c8141af0e05cf), [Reference 2](https://github.com/argoproj/argo-cd/releases/tag/v2.1.14), [Reference 3](https://github.com/argoproj/argo-cd/releases/tag/v2.2.8).