Argo Workflows Allows Access to Archived Workflows with Fake Token in `client` mode
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| argoproj | argo-workflows | affected |
|
Configuration 1 [-]
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-3475 | Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. When using `--auth-mode=client`, Archived Workflows can be retrieved with a fake or spoofed token via the GET Workflow endpoint: `/api/v1/workflows/{namespace}/{name}` or when using `--auth-mode=sso`, all Archived Workflows can be retrieved with a valid token via the GET Workflow endpoint: `/api/v1/workflows/{namespace}/{name}`. No authentication is performed by the Server itself on `client` tokens. Authentication & authorization is instead delegated to the k8s API server. However, the Workflow Archive does not interact with k8s, and so any token that looks valid will be considered authenticated, even if it is not a k8s token or even if the token has no RBAC for Argo. To handle the lack of pass-through k8s authN/authZ, the Workflow Archive specifically does the equivalent of a `kubectl auth can-i` check for respective methods. In 3.5.7 and 3.5.8, the auth check was accidentally removed on the GET Workflow endpoint's fallback to archived workflows on these lines, allowing archived workflows to be retrieved with a fake token. This vulnerability is fixed in 3.6.2 and 3.5.13. |
Github GHSA |
GHSA-h36c-m3rf-34h9 | Access to Archived Argo Workflows with Fake Token in `client` mode |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.660% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Argoproj argo Workflows
|
|
| CPEs | cpe:2.3:a:argoproj:argo_workflows:*:*:*:*:*:go:*:* | |
| Vendors & Products |
Argo Workflows Project
Argo Workflows Project argo Workflows |
Argoproj argo Workflows
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Argo Workflows Project
Argo Workflows Project argo Workflows |
|
| CPEs | cpe:2.3:a:argo_workflows_project:argo_workflows:*:*:*:*:*:kubernetes:*:* | |
| Vendors & Products |
Argo Workflows Project
Argo Workflows Project argo Workflows |
|
| Metrics |
cvssV3_1
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Argoproj
Argoproj argo-workflows |
|
| CPEs | cpe:2.3:a:argoproj:argo-workflows:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Argoproj
Argoproj argo-workflows |
|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Argo Workflows is an open source container-native workflow engine for orchestrating parallel jobs on Kubernetes. When using `--auth-mode=client`, Archived Workflows can be retrieved with a fake or spoofed token via the GET Workflow endpoint: `/api/v1/workflows/{namespace}/{name}` or when using `--auth-mode=sso`, all Archived Workflows can be retrieved with a valid token via the GET Workflow endpoint: `/api/v1/workflows/{namespace}/{name}`. No authentication is performed by the Server itself on `client` tokens. Authentication & authorization is instead delegated to the k8s API server. However, the Workflow Archive does not interact with k8s, and so any token that looks valid will be considered authenticated, even if it is not a k8s token or even if the token has no RBAC for Argo. To handle the lack of pass-through k8s authN/authZ, the Workflow Archive specifically does the equivalent of a `kubectl auth can-i` check for respective methods. In 3.5.7 and 3.5.8, the auth check was accidentally removed on the GET Workflow endpoint's fallback to archived workflows on these lines, allowing archived workflows to be retrieved with a fake token. This vulnerability is fixed in 3.6.2 and 3.5.13. | |
| Title | Argo Workflows Allows Access to Archived Workflows with Fake Token in `client` mode | |
| Weaknesses | CWE-200 CWE-290 |
|
| References |
| |
| Metrics |
cvssV4_0
|