Authenticated processing halt via malformed duration fields
Published Oct 21, 2022 · Updated Apr 23, 2025
Improper input validation in Flux before 0.35.0 allows remote authenticated users to halt processing for an entire object type. Flux controllers accept invalid values in .spec.interval, .spec.timeout, and structured variants because metav1.Duration is incompatible with time.Duration and the fields lack validation. Permission to change Flux objects through a source or the Kubernetes API is required, and one malformed value stops reconciliation for every object of that type.
Summary
What happened
Improper input validation in Flux before 0.35.0 allows remote authenticated users to halt processing for an entire object type. Flux controllers accept invalid values in .spec.interval, .spec.timeout, and structured variants because metav1.Duration is incompatible with time.Duration and the fields lack validation. Permission to change Flux objects through a source or the Kubernetes API is required, and one malformed value stops reconciliation for every object of that type.
The record
- CVE
- CVE-2022-39272
- Published
- Oct 21, 2022
- Updated
- Apr 23, 2025
- Vendor
- Flux CD
- Product
- Flux
- Classifications
- CWE-20, CWE-1284, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 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.35.0
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
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