Skip to content
Fencer Vulns
critical 9.1

CVE-2023-23947 json

Argo CD users with any cluster secret update access may update out-of-bounds cluster secrets

published 2023-02-16 3 y ago modified 2026-09-10 1 mo ago also GHSA-3jfq-742w-xg8j , GO-2023-1577 , EUVD-2023-0613

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/argoproj/argo-cd 2.3.17, 2.4.23, 2.5.11, 2.6.2
  • go github.com/argoproj/argo-cd/v2 2.3.17, 2.4.23, 2.5.11, 2.6.2
  • argoproj argo_cd 2.3.17, 2.4.23, 2.5.11, 2.6.2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-23947 updated cvss 9.1

ArgoCD: Users with any cluster secret update access may update out-of-bounds cluster secrets

  • Red Hat OpenShift GitOps 1.5 openshift-gitops-1/argocd-rhel8 v1.5.10-6
    fixed: vendor fix RHSA-2023:0804
  • Red Hat OpenShift GitOps 1.6 openshift-gitops-1/argocd-rhel8 v1.6.5-5
    fixed: vendor fix RHSA-2023:0802
  • Red Hat OpenShift GitOps 1.7 openshift-gitops-1/argocd-rhel8 v1.7.2-5
    fixed: vendor fix RHSA-2023:0803
  • Red Hat OpenShift GitOps 1.5 openshift-gitops-1/dex-rhel8 v1.5.10-6, openshift-gitops-1/gitops-rhel8 v1.5.10-6, openshift-gitops-1/kam-delivery-rhel8 v1.5.10-6, openshift-gitops-1/applicationset-rhel8 v1.5.10-6, openshift-gitops-1/gitops-rhel8-operator v1.5.10-6, openshift-gitops-1/gitops-operator-bundle v1.5.10-5 Red Hat OpenShift GitOps 1.6 openshift-gitops-1/dex-rhel8 v1.6.5-5, openshift-gitops-1/gitops-rhel8 v1.6.5-5, openshift-gitops-1/kam-delivery-rhel8 v1.6.5-5, openshift-gitops-1/gitops-rhel8-operator v1.6.5-5, openshift-gitops-1/gitops-operator-bundle v1.6.5-5 Red Hat OpenShift GitOps 1.7 openshift-gitops-1/dex-rhel8 v1.7.2-5, openshift-gitops-1/gitops-rhel8 v1.7.2-5, openshift-gitops-1/kam-delivery-rhel8 v1.7.2-5, openshift-gitops-1/console-plugin-rhel8 v1.7.2-5, openshift-gitops-1/gitops-rhel8-operator v1.7.2-5, openshift-gitops-1/gitops-operator-bundle v1.7.2-5
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
19 mo ago

Exploit prediction

0.67% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 8.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/argoproj/argo-cd
>=2.3.0, <2.3.17
>=2.4.0, <2.4.23
>=2.5.0, <2.5.11
>=2.6.0, <2.6.2
all versions
2.3.17
2.4.23
2.5.11
2.6.2
go github.com/argoproj/argo-cd/v2
>=2.3.0, <2.3.17
>=2.4.0, <2.4.23
>=2.5.0, <2.5.11
>=2.6.0, <2.6.2
2.3.17
2.4.23
2.5.11
2.6.2

Affected products

  • argoproj argo-cd

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.