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

Users with `create` but not `override` privileges can perform local sync in argo-cd

cve-program · CVE-2023-50726

Published

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. "Local sync" is an Argo CD feature that allows developers to temporarily override an Application's manifests with locally-defined manifests. Use of the feature should generally be limited to highly-trusted users, since it allows the user to bypass any merge protections in git. An improper validation bug allows users who have `create` privileges but not `override` privileges to sync local manifests on app creation. All other restrictions, including AppProject restrictions are still enforced. The only restriction which is not enforced is that the manifests come from some approved git/Helm/OCI source. The bug was introduced in 1.2.0-rc1 when the local manifest sync feature was added. The bug has been patched in Argo CD versions 2.10.3, 2.9.8, and 2.8.12. Users are advised to upgrade. Users unable to upgrade may mitigate the risk of branch protection bypass by removing `applications, create` RBAC access. The only way to eliminate the issue without removing RBAC access is to upgrade to a patched version.

Read the publisher's advisory

euvd · EUVD-2024-0926

Published

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. "Local sync" is an Argo CD feature that allows developers to temporarily override an Application's manifests with locally-defined manifests. Use of the feature should generally be limited to highly-trusted users, since it allows the user to bypass any merge protections in git. An improper validation bug allows users who have `create` privileges but not `override` privileges to sync local manifests on app creation. All other restrictions, including AppProject restrictions are still enforced. The only restriction which is not enforced is that the manifests come from some approved git/Helm/OCI source. The bug was introduced in 1.2.0-rc1 when the local manifest sync feature was added. The bug has been patched in Argo CD versions 2.10.3, 2.9.8, and 2.8.12. Users are advised to upgrade. Users unable to upgrade may mitigate the risk of branch protection bypass by removing `applications, create` RBAC access. The only way to eliminate the issue without removing RBAC access is to upgrade to a patched version.

Read the publisher's advisory

nvd · CVE-2023-50726

Published

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. "Local sync" is an Argo CD feature that allows developers to temporarily override an Application's manifests with locally-defined manifests. Use of the feature should generally be limited to highly-trusted users, since it allows the user to bypass any merge protections in git. An improper validation bug allows users who have `create` privileges but not `override` privileges to sync local manifests on app creation. All other restrictions, including AppProject restrictions are still enforced. The only restriction which is not enforced is that the manifests come from some approved git/Helm/OCI source. The bug was introduced in 1.2.0-rc1 when the local manifest sync feature was added. The bug has been patched in Argo CD versions 2.10.3, 2.9.8, and 2.8.12. Users are advised to upgrade. Users unable to upgrade may mitigate the risk of branch protection bypass by removing `applications, create` RBAC access. The only way to eliminate the issue without removing RBAC access is to upgrade to a patched version.

Read the publisher's advisory

osv · GHSA-g623-jcgg-mhmm

Published

### Impact "Local sync" is an Argo CD feature that allows developers to temporarily override an Application's manifests with locally-defined manifests. Use of the feature should generally be limited to highly-trusted users, since it allows the user to bypass any merge protections in git. An improper validation bug allows users who have `create` privileges but not `override` privileges to sync local manifests on app creation. All other restrictions, including AppProject restrictions are still enforced. The only restriction which is _not_ enforced is that the manifests come from some approved git/Helm/OCI source. The bug was introduced in 1.2.0-rc1 when the local manifest sync feature was added. ### Patches The bug has been patched in the following versions: * 2.10.3 * 2.9.8 * 2.8.12 ### Workarounds To immediately mitigate the risk of branch protection bypass, remove `applications, create` RBAC access. The only way to eliminate the issue without removing RBAC access is to upgrade to a patched version. Branch protection rules and review requirements are a great way to enforce security constraints in a GitOps environment, but they should be just one layer in a multi-layered approach. Make sure your AppProject and RBAC restrictions are as thorough as possible to prevent a review bypass vulnerability from permitting excessive damage. ### References * [Argo CD RBAC documentation](https://argo-cd.readthedocs.io/en/latest/operator-manual/rbac/) ### 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-2024-2643

Published

An improper validation bug allows users who have create privileges to sync a local manifest during application creation. This allows for bypassing the restriction that the manifests come from some approved git/Helm/OCI source.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2023-50726

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": ">= 1.2.0-rc1, < 2.8.12",
                            "status": "affected"
                        },
                        {
                            "version": ">= 2.9.0, < 2.9.8",
                            "status": "affected"
                        },
                        {
                            "version": ">= 2.10.0, < 2.10.3",
                            "status": "affected"
                        }
                    ]
                }

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

euvd · EUVD-2024-0926

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: Mar 13, 2024, 8:50:52 PM

dateUpdated: Apr 15, 2025, 3:17:37 PM

5 related source bulletins · separate from aliases

RHSA-2024:1700: Red Hat Security Advisory: Errata Advisory for Red Hat OpenShift GitOps v1.10.4 security update

CVE-2023-50726 · CVE-2024-21652 · CVE-2024-21661 · CVE-2024-21662 · CVE-2024-29893

RHSA-2024:1697: Red Hat Security Advisory: Errata Advisory for Red Hat OpenShift GitOps v1.11.3 security update

CVE-2023-50726 · CVE-2024-21652 · CVE-2024-21661 · CVE-2024-21662 · CVE-2024-29893

WID-SEC-W-2024-0812: Red Hat OpenShift: Mehrere Schwachstellen

CVE-2024-21661 · CVE-2024-29893 · CVE-2023-50726 · CVE-2024-21652 · CVE-2024-21662

RHSA-2024:1753: Red Hat Security Advisory: Errata Advisory for Red Hat OpenShift GitOps v1.12.1 security update

CVE-2023-50726 · CVE-2024-21652 · CVE-2024-21661 · CVE-2024-21662 · CVE-2024-29893

RHSA-2024:1752: Red Hat Security Advisory: GitOps 1.12.1- Argo CD CLI and MicroShift GitOps security update

CVE-2023-50726 · CVE-2024-21652 · CVE-2024-21661 · CVE-2024-21662 · CVE-2024-29893

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-50726

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: Analyzed

Weakness classifications: CWE-269 · CWE-863

Original publisher date fields

published: 2024-03-13T21:15:54.797

lastModified: 2026-06-17T06:39:51.930

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-g623-jcgg-mhmm

Published

github.com/argoproj/argo-cd

Go

SEMVER · introduced 1.2.0-rc1 → last_affected 1.8.7

github.com/argoproj/argo-cd/v2

Go

SEMVER · introduced 2.9.0 → fixed 2.9.8

github.com/argoproj/argo-cd/v2

Go

SEMVER · introduced 2.10.0 → fixed 2.10.3

github.com/argoproj/argo-cd/v2

Go

SEMVER · introduced 2.0.0-rc3 → fixed 2.8.12

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

osv · GO-2024-2643

Published

github.com/argoproj/argo-cd

Go

SEMVER · introduced 1.2.0-rc1

github.com/argoproj/argo-cd/v2

Go

SEMVER · introduced 2.0.0 → fixed 2.8.12 → introduced 2.9.0 → fixed 2.9.8 → introduced 2.10.0 → fixed 2.10.3

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 22 Nov 16:32 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current