Archived workflow disclosure via omitted authorization check
Published Dec 2, 2024 · Updated Dec 2, 2024
Authentication bypass in Argo Workflows 3.5.7 through 3.5.12 and 3.6.0-rc1 through 3.6.1 allows remote attackers to read archived workflows. The GET Workflow handler falls back to the workflow archive without performing the equivalent Kubernetes authorization check, so a fabricated client token or insufficiently authorized SSO token is accepted. Exploitation requires an enabled workflow archive and client or SSO authentication mode; the demonstrated consequence is unauthorized disclosure of archived workflow definitions and status data.
Summary
What happened
Authentication bypass in Argo Workflows 3.5.7 through 3.5.12 and 3.6.0-rc1 through 3.6.1 allows remote attackers to read archived workflows. The GET Workflow handler falls back to the workflow archive without performing the equivalent Kubernetes authorization check, so a fabricated client token or insufficiently authorized SSO token is accepted. Exploitation requires an enabled workflow archive and client or SSO authentication mode; the demonstrated consequence is unauthorized disclosure of archived workflow definitions and status data.
The record
- CVE
- CVE-2024-53862
- Published
- Dec 2, 2024
- Updated
- Dec 2, 2024
- Vendor
- Argo Project
- Product
- Argo Workflows
- Classifications
- CWE-290, CWE-862, CWE-200, CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 2, 2024CVE publishedPublication date reported by the CVE source.
- Dec 2, 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 <3.5.13
- Affected versionversion=0 <=3.5.7
- Affected versionversion=0 <=3.6.0-rc1
- Affected versionversion=0 <3.6.2
- Affected versionversion=>= 3.5.7, < 3.5.13
- Affected versionversion=>= 3.6.0-rc1, < 3.6.2
What conditions does exploitation require?
What is affected?
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
- GHSA-h36c-m3rf-34h9 archived-workflow reproductionproof 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