# GHSA-6w87-g839-9wv7: Helm OCI credentials leaked into Argo CD logs

> Attackers with log access can steal Helm OCI repository credentials leaked by Argo CD, requiring an upgrade and credential rotation.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 May 2021
- **Also known as:** GO-2022-0387

## What is GHSA-6w87-g839-9wv7?

GHSA-6w87-g839-9wv7 is a vulnerability in github.com/argoproj/argo-cd, published on 21 May 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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:

* 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`

### 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.

## Which versions are affected by GHSA-6w87-g839-9wv7?

5 open source packages ship an affected version, including github.com/argoproj/argo-cd.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/argoproj/argo-cd` | Go | All versions | 1.7.14, 1.8.7 |
| `github.com/argoproj/argo-cd` | Go | All versions | 1.7.14 |
| `github.com/argoproj/argo-cd` | Go | All versions | 1.7.14 |
| `github.com/argoproj/argo-cd` | Go | From 1.8.0 | 1.8.7 |
| `github.com/argoproj/argo-cd` | Go | From 1.8.0 | 1.8.7 |

## How do I fix GHSA-6w87-g839-9wv7?

Upgrade github.com/argoproj/argo-cd to a fixed version for your release line: 1.7.14 or 1.8.7.

## Is GHSA-6w87-g839-9wv7 being exploited?

There is no known exploitation of GHSA-6w87-g839-9wv7 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-6w87-g839-9wv7 and fix it if it is affected.

What it is: GHSA-6w87-g839-9wv7 is a vulnerability in github.com/argoproj/argo-cd, published on 21 May 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-6w87-g839-9wv7 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/argoproj/argo-cd (Go): affected all versions; fixed in 1.7.14, 1.8.7
- github.com/argoproj/argo-cd (Go): affected all versions; fixed in 1.7.14
- github.com/argoproj/argo-cd (Go): affected all versions; fixed in 1.7.14
- github.com/argoproj/argo-cd (Go): affected from 1.8.0; fixed in 1.8.7
- github.com/argoproj/argo-cd (Go): affected from 1.8.0; fixed in 1.8.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-6w87-g839-9wv7/ (Markdown: https://insights.sbomify.com/GHSA-6w87-g839-9wv7/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-6w87-g839-9wv7

---
From sbomify Insights: https://insights.sbomify.com/GHSA-6w87-g839-9wv7/
Summaries are generated and may contain mistakes; the official description above is the record.