Skip to content

Helm OCI credentials leaked into Argo CD logs

Moderate severity GitHub Reviewed Published Mar 8, 2021 in argoproj/argo-cd • Updated Jan 9, 2023

Package

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

Affected versions

< 1.7.14
>= 1.8.0, < 1.8.7

Patched versions

1.7.14
1.8.7

Description

Impact

When Argo CD was connected to a Helm OCI repository with authentication enabled, the credentials used for accessing the remote repository were logged.

Anyone with access to the pod logs - either via access with appropriate permissions to the Kubernetes control plane or a third party log management system where the logs from Argo CD were aggregated - could have potentially obtained the credentials to the Helm OCI repository.

If you are using Helm OCI repositories with Argo CD, it is strongly recommended to upgrade Argo CD to the latest patch version and to change the credentials used to access the repositories.

Patches

A patch for this vulnerability is available with the v1.8.7 and v1.7.14 releases of Argo CD.

Workarounds

No workaround available

References

N/A

For more information

If you have any questions or comments about this advisory:

Credits

This vulnerability was found and reported by a third-party who wishes to stay anonymous. We want to thank this third-party for disclosing this vulnerability to us in a responsible manner.

References

@alexmt alexmt published to argoproj/argo-cd Mar 8, 2021
Reviewed May 21, 2021
Published to the GitHub Advisory Database May 21, 2021
Last updated Jan 9, 2023

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
Local
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
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:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-6w87-g839-9wv7

Source code

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