Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2024-53862— Argo Workflows Allows Access to Archived Workflows with Fake Token in `client` mode

Quick assessment

Affected
argoproj argo-workflows
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Argo Workflows是Argo项目的一个用于 Kubernetes 的开源容器原生工作流引擎。 Argo Workflows 3.5.7及之前版本存在安全漏洞,该漏洞源于对存档工作流的GET Workflow端点进行访问时意外移除了权限检查,导致可以使用伪造的令牌获取存档的工作流。

AI Predicted 8.1 Difficulty: Easy EPSS 0.66% · P50

Possible ATT&CK Techniques 1 AI

T1078.004 · Cloud Accounts
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2024-53862

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Argo Workflows Allows Access to Archived Workflows with Fake Token in `client` mode
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N
Source: CVE Program / CVE List V5
Vulnerability Type
信息暴露
Source: CVE Program / CVE List V5
Vulnerability Title
Argo Workflows 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Argo Workflows是Argo项目的一个用于 Kubernetes 的开源容器原生工作流引擎。 Argo Workflows 3.5.7及之前版本存在安全漏洞,该漏洞源于对存档工作流的GET Workflow端点进行访问时意外移除了权限检查,导致可以使用伪造的令牌获取存档的工作流。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
argoproj argo-workflows >= 3.5.7, < 3.5.13 -

II. Public POCs for CVE-2024-53862

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-53862

请登录查看更多情报信息。

Patches & Fixes for CVE-2024-53862 (1)

Vendor Advisories for CVE-2024-53862 (1)

IV. Related Vulnerabilities

V. Comments for CVE-2024-53862

No comments yet


Leave a comment