Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/fluxcd/helm-controller/api

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.0GoPublished

    Improper use of metav1.Duration allows for Denial of Service

    CVE-2022-39272 · GHSA-f4p5-x4vc-mh4v

    Affected
    • Go github.com/fluxcd/helm-controller/api < 0.26.0
    Fixed in
    0.26.0· Vendor fix available
    Issue
    Flux controllers within the affected versions range are vulnerable to a denial of service attack. Users that have permissions to change Flux’s objects, either through a Flux source or directly within a cluster, can provide invalid data to fields .spec.interval or .spec.timeout (and structured variations of these fields), causing the entire object type to stop being processed. The issue has two root causes: a) the Kubernetes type metav1.Duration not being fully compatible with the Go type time.Duration as explained on upstream report; b) lack of validation within Flux to restrict allowed values. Workarounds Admission controllers can be employed to restrict the values that can be used for fields .spec.interval and .spec.timeout, however upgrading to the latest versions is still the recommended mitigation. Credits This issue was reported by Alexander Block (@codablock) through the Flux security mailing list (as recommended). For more information If you have any questions or comments…

    Recommended action: Upgrade to 0.26.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →