Namespace code execution via excessive workflow-role permissions
Published Nov 21, 2024 · Updated Nov 21, 2024
Excessive privileges in Argo Workflows Chart before 0.44.0 allow local users to execute code in any Pod in the same namespace. The workflow-role template grants create on pods/exec, although the Emissary executor used by appVersion 3.4 and later does not require it. Exploitation requires a malicious workflow template to use the chart-created service account, which is not installed by default, and exposes the namespace's Pods.
Summary
What happened
Excessive privileges in Argo Workflows Chart before 0.44.0 allow local users to execute code in any Pod in the same namespace. The workflow-role template grants create on pods/exec, although the Emissary executor used by appVersion 3.4 and later does not require it. Exploitation requires a malicious workflow template to use the chart-created service account, which is not installed by default, and exposes the namespace's Pods.
The record
- CVE
- CVE-2024-52799
- Published
- Nov 21, 2024
- Updated
- Nov 21, 2024
- Vendor
- Argo Project
- Product
- Argo Helm Charts
- Classifications
- CWE-250, CWE-1220, T1609
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 21, 2024CVE publishedPublication date reported by the CVE source.
- Nov 21, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.44.0
- Affected versionversion=< 0.44.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Malicious workflow pods/exec proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo