Status-report manipulation via overbroad workflow role
Published Nov 22, 2024 · Updated Nov 22, 2024
Improper access control in the Argo Workflows chart before 0.45.0 allows local users to alter status reporting through crafted templates. The workflow-role grants every workflow Pod access to workflowtasksets and workflowartifactgctasks instead of restricting those permissions to Agent and ArtifactGC Pods. Exploitation requires a low-privileged user and execution of a malicious HTTP, Plugin, or ArtifactGC workflow; the consequence is limited to status integrity.
Summary
What happened
Improper access control in the Argo Workflows chart before 0.45.0 allows local users to alter status reporting through crafted templates. The workflow-role grants every workflow Pod access to workflowtasksets and workflowartifactgctasks instead of restricting those permissions to Agent and ArtifactGC Pods. Exploitation requires a low-privileged user and execution of a malicious HTTP, Plugin, or ArtifactGC workflow; the consequence is limited to status integrity.
The record
- CVE
- CVE-2024-52814
- Published
- Nov 22, 2024
- Updated
- Nov 22, 2024
- Vendor
- Argo Project
- Product
- Argo Helm Charts
- Classifications
- CWE-1220
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 22, 2024CVE publishedPublication date reported by the CVE source.
- Nov 22, 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.45.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
No public exploit references are available in this record.
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