Kubernetes workload injection via namespace path traversal
Published Aug 31, 2022 · Updated Apr 23, 2025
Path traversal in Flux CLI before 0.32.0 allows local users to replace Kubernetes deployment content through a crafted namespace. The root command accepted the --namespace flag and FLUX_SYSTEM_NAMESPACE value without DNS-label validation, allowing traversal elements to redirect generated deployment paths. Exploitation requires another application sharing the shell environment and a subsequent Flux CLI deployment, which can install attacker-chosen content in the target cluster.
Summary
What happened
Path traversal in Flux CLI before 0.32.0 allows local users to replace Kubernetes deployment content through a crafted namespace. The root command accepted the --namespace flag and FLUX_SYSTEM_NAMESPACE value without DNS-label validation, allowing traversal elements to redirect generated deployment paths. Exploitation requires another application sharing the shell environment and a subsequent Flux CLI deployment, which can install attacker-chosen content in the target cluster.
The record
- CVE
- CVE-2022-36035
- Published
- Aug 31, 2022
- Updated
- Apr 23, 2025
- Vendor
- Flux CD
- Product
- Flux
- Classifications
- CWE-22, T1610
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 31, 2022CVE publishedPublication date reported by the CVE source.
- Apr 23, 2025Record 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.32.0, >= 0.21.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