# GHSA-rc7p-gmvh-xfx2: Attack on Kubernetes via Misconfigured Argo Workflows

> Remote attackers can execute arbitrary code on Kubernetes clusters if Argo Server UI is exposed with default server auth mode.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Aug 2021

## What is GHSA-rc7p-gmvh-xfx2?

GHSA-rc7p-gmvh-xfx2 is a vulnerability in github.com/argoproj/argo-workflows, published on 2 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Impact

Users running using the Argo Server with `--auth-mode=server` (which is the default < v3.0.0) AND have exposed their UI to the Internet may allow remote users to execute arbitrary code on their cluster, e.g. crypto-mining.

### Resolution

* Do not expose your user interface to the Internet. 
* Change configuration. `--auth-mode=client`. 

For users using an older 2.x version of Argo Server, consider upgrading to Argo Server version 3.x or later.

## Which versions are affected by GHSA-rc7p-gmvh-xfx2?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/argoproj/argo-workflows` | Go | All versions | None |
| `github.com/argoproj/argo-workflows` | Go | All versions | None |

## How do I fix GHSA-rc7p-gmvh-xfx2?

No fix has been published for GHSA-rc7p-gmvh-xfx2 yet. Limit exposure of the affected software until one is available.

## Is GHSA-rc7p-gmvh-xfx2 being exploited?

There is no known exploitation of GHSA-rc7p-gmvh-xfx2 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-rc7p-gmvh-xfx2 and fix it if it is affected.

What it is: GHSA-rc7p-gmvh-xfx2 is a vulnerability in github.com/argoproj/argo-workflows, published on 2 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-rc7p-gmvh-xfx2 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/argoproj/argo-workflows (Go): affected all versions; no fix listed
- github.com/argoproj/argo-workflows (Go): affected all versions; no fix listed

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-rc7p-gmvh-xfx2/ (Markdown: https://insights.sbomify.com/GHSA-rc7p-gmvh-xfx2/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-rc7p-gmvh-xfx2

---
From sbomify Insights: https://insights.sbomify.com/GHSA-rc7p-gmvh-xfx2/
Summaries are generated and may contain mistakes; the official description above is the record.