Skip to content

Users with `create` but not `override` privileges can perform local sync

Moderate severity GitHub Reviewed Published Mar 13, 2024 in argoproj/argo-cd • Updated Mar 15, 2024

Package

gomod github.com/argoproj/argo-cd (Go)

Affected versions

>= 1.2.0-rc1, <= 1.8.7

Patched versions

None
gomod github.com/argoproj/argo-cd/v2 (Go)
>= 2.9.0, < 2.9.8
>= 2.10.0, < 2.10.3
>= 2.0.0-rc3, < 2.8.12
2.9.8
2.10.3
2.8.12

Description

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

For more information

References

@crenshaw-dev crenshaw-dev published to argoproj/argo-cd Mar 13, 2024
Published by the National Vulnerability Database Mar 13, 2024
Published to the GitHub Advisory Database Mar 15, 2024
Reviewed Mar 15, 2024
Last updated Mar 15, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L

EPSS score

0.045%
(16th percentile)

Weaknesses

CVE ID

CVE-2023-50726

GHSA ID

GHSA-g623-jcgg-mhmm

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.