Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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

cve-program · CVE-2023-23947

Published

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.

Read the publisher's advisory

euvd · EUVD-2023-0613

Published

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.

Read the publisher's advisory

nvd · CVE-2023-23947

Published

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.

Read the publisher's advisory

osv · GHSA-3jfq-742w-xg8j

Published

### Impact All Argo CD versions starting with v2.3.0-rc1 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). #### How the Attack Works Argo CD stores [cluster access configurations](https://argo-cd.readthedocs.io/en/stable/operator-manual/declarative-setup/#clusters) as Kubernetes Secrets. To take advantage of the vulnerability, an attacker must know the server URL for the cluster secret they want to modify. The attacker must be authenticated with the Argo CD API server, and they must be authorized to update at least one ([non project-scoped](https://argo-cd.readthedocs.io/en/stable/user-guide/projects/#project-scoped-repositories-and-clusters)) cluster. Then they must craft a malicious request to the Argo CD API server. #### Removing Deployment Restrictions A cluster Secret's `clusterResources` field determines whether Argo CD users may deploy cluster-scoped resources to that cluster. The `namespaces` field determines the namespaces to which Argo CD users may deploy resources. You can use this command to determine whether any of your cluster configurations employ these restrictions (replace `argocd` with the namespace of your Argo CD installation): ```shell kubectl get secret -n argocd -l 'argocd.argoproj.io/secret-type=cluster' -ojson | jq '.items | map(.data |= with_entries(.value |= @base64d)) | # base64-decode secrets map(select(.data | ( (.clusterResources != null and .clusterResources == "false") or # we deny cluster-scoped resource management (.namespaces != null and .namespaces != "") # we are only managing certain clusters )) | .metadata.name)' ``` The `clusterResources` and `namespaces` fields are one line of defense against unauthorized management of Kubernetes resources. Users should also have AppProject and RBAC restrictions in place. If `clusterResources: "false"` or `namespaces: "some,namespaces"` are the _only_ mechanisms preventing an attacker from maliciously managing certain resources via Argo CD, then this vulnerability could allow that attacker to manage out-of-bounds resources via Argo CD (create, get, update, delete). #### Modifying Connection Parameters Cluster secrets also hold client configuration for connecting to the remote cluster. One option is to skip TLS certificate verification. An attacker could disable certificate verification in an effort to achieve a malicious-in-the-middle (MITM) attack. Alternatively, an attacker could apply an invalid configuration (for example, by setting an invalid bearer token) and achieve a denial-of-service by preventing Argo CD from managing the target cluster. #### Changing Unscoped Clusters to be Scoped The vulnerability also allows an attacker to modify a previously-unscoped cluster and make it [scoped](https://argo-cd.readthedocs.io/en/stable/user-guide/projects/#project-scoped-repositories-and-clusters). This is important if you are using `permitOnlyProjectScopedClusters: true` in a project under which the attacker can deploy. By scoping a previously-unscoped cluster under that project, they can grant themselves the ability to manage resources on the target cluster. ### Patches A patch for this vulnerability has been released in the following Argo CD versions: * v2.6.2 * v2.5.11 * v2.4.23 * v2.3.17 ### Workarounds The best way to mitigate the vulnerability is to upgrade. The following two sections explain other ways to mitigate the vulnerability if you are currently unable to upgrade. #### Limit Users with Cluster Update Access The only complete mitigation besides upgrading is to modify your RBAC configuration to completely revoke all `clusters, update` access. To exploit this vulnerability, an attacker must have access to update at least one cluster configuration. Check your [RBAC configuration](https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/), for lines like this: ``` p, role:developers, clusters, update, *, allow p, role:developers, clusters, *, *, allow p, role:developers, *, update, *, allow ``` Revoke `clusters, update` access for any users who do not absolutely need that access. #### Restrict Resource Management via AppProjects and RBAC [AppProjects](https://argo-cd.readthedocs.io/en/stable/user-guide/projects/#projects) are a primary tool to restrict what resources may be managed via Argo CD. You can use the `destinations` and `clusterResourceWhitelist` fields to apply similar restrictions as the `namespaces` and `clusterResources` fields described above. ```yaml apiVersion: argoproj.io/v1alpha1 kind: AppProject spec: destinations: # Only allow Applications managed by this AppProject to manage to the `allowed-namespace` namespace. - namespace: 'allowed-namespace' server: 'https://your-server' # Do not allow Applications managed by this AppProject to manage any cluster-scoped resources. clusterResourceWhitelist: [] ``` Along with adding AppProject restrictions, make sure that your RBAC restrictions are strict enough. For example, limit `projects, update` access to Argo CD administrators only. Also use the `{project}` field in `applications, *, {project}/{application}` field to limit users' access to certain, restricted, AppProjects. AppProject restrictions can only prevent Applications from managing out-of-bounds resources. It cannot prevent an attacker from maliciously changing cluster connection TLS configuration. ### For more information * Open an issue in [the Argo CD issue tracker](https://github.com/argoproj/argo-cd/issues) or [discussions](https://github.com/argoproj/argo-cd/discussions) * Join us on [Slack](https://argoproj.github.io/community/join-slack) in channel #argo-cd

Read the publisher's advisory

osv · GO-2023-1577

Published

Users with any cluster secret update access may update out-of-bounds cluster secrets in github.com/argoproj/argo-cd

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2023-23947

Published

argo-cd

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "argoproj",
                    "product": "argo-cd",
                    "versions": [
                        {
                            "version": ">= 2.3.0-rc1, < 2.3.17",
                            "status": "affected"
                        },
                        {
                            "version": ">= 2.4.0, < 2.4.23",
                            "status": "affected"
                        },
                        {
                            "version": ">= 2.5.0, < 2.5.11",
                            "status": "affected"
                        },
                        {
                            "version": ">= 2.6.0, < 2.6.2",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2023-0613

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Feb 16, 2023, 5:39:27 PM

dateUpdated: Mar 10, 2025, 9:10:20 PM

3 related source bulletins · separate from aliases

RHSA-2023:0803: Red Hat Security Advisory: Red Hat OpenShift GitOps security update

CVE-2021-4238 · CVE-2022-3064 · CVE-2023-23947

RHSA-2023:0802: Red Hat Security Advisory: Red Hat OpenShift GitOps security update

CVE-2021-4238 · CVE-2022-3064 · CVE-2023-23947

RHSA-2023:0804: Red Hat Security Advisory: Red Hat OpenShift GitOps security update

CVE-2021-4238 · CVE-2022-3064 · CVE-2023-23947

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2023-23947

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-863

Original publisher date fields

published: 2023-02-16T18:15:11.310

lastModified: 2026-06-17T05:38:20.940

1 source CPE criteria · context only
  • cpe:2.3:a:argoproj:argo_cd:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-3jfq-742w-xg8j

Published

github.com/argoproj/argo-cd

Go

SEMVER · introduced 2.3.0 → fixed 2.3.17

github.com/argoproj/argo-cd

Go

SEMVER · introduced 2.4.0 → fixed 2.4.23

github.com/argoproj/argo-cd

Go

SEMVER · introduced 2.5.0 → fixed 2.5.11

github.com/argoproj/argo-cd

Go

SEMVER · introduced 2.6.0 → fixed 2.6.2

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2023-1577

Published

github.com/argoproj/argo-cd

Go

SEMVER · introduced 0

github.com/argoproj/argo-cd/v2

Go

SEMVER · introduced 2.3.0 → fixed 2.3.17 → introduced 2.4.0 → fixed 2.4.23 → introduced 2.5.0 → fixed 2.5.11 → introduced 2.6.0 → fixed 2.6.2

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 04:49 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current