Skip to content

Argo CD GitOps Engine does not scrub secret values from patch errors

Moderate severity GitHub Reviewed Published Jan 30, 2025 in argoproj/gitops-engine

Package

gomod github.com/argoproj/gitops-engine (Go)

Affected versions

<= 0.7.3

Patched versions

None

Description

Impact

A vulnerability was discovered in Argo CD that exposed secret values in error messages and the diff view when an invalid Kubernetes Secret resource was synced from a repository.

The vulnerability assumes the user has write access to the repository and can exploit it, either intentionally or unintentionally, by committing an invalid Secret to repository and triggering a Sync. Once exploited, any user with read access to Argo CD can view the exposed secret data.

Patches

A patch for this vulnerability is available in the following Argo CD versions:

  • v2.13.4
  • v2.12.10
  • v2.11.13

Workarounds

There is no workaround other than upgrading.

References

Fixed with commit argoproj/argo-cd@6f5537b & argoproj/gitops-engine@7e21b91

References

@jannfis jannfis published to argoproj/gitops-engine Jan 30, 2025
Published to the GitHub Advisory Database Jan 30, 2025
Reviewed Jan 30, 2025

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

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:H/UI:N/S:C/C:H/I:N/A:N

EPSS score

Weaknesses

No CWEs

CVE ID

No known CVE

GHSA ID

GHSA-274v-mgcv-cm8j

Source code

Credits

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