Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/metal3-io/cluster-api-provider-metal3

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.5GoPublished

    CAPM3 vulnerable to Cross-Namespace resource access

    GHSA-rf84-wr5g-m3rp

    Affected
    • Go github.com/metal3-io/cluster-api-provider-metal3 <= 1.11.7; >= 1.12.0, <= 1.12.4
    Fixed in
    1.11.81.12.5· Vendor fix available
    Issue
    CAPM3 is Metal3's Cluster API (CAPI) provider for baremetal provisioning in Kubernetes. Multiple cross-namespace access control vulnerabilities in Cluster API Provider Metal3 allow users with permissions to create or modify CAPM3 resources in one namespace to reference, read, or claim resources belonging to other namespaces. Patched In - v1.13.0 (main branch — all fixes included) - v1.12.5 (all four fixes backported) - v1.11.8 (three of four fixes backported; Metal3DataClaim template restriction not applicable due to missing v1beta2 webhook infrastructure) Description Four related vulnerabilities were identified and fixed: 1. Cross-namespace Secret references in Metal3Machine Metal3Machine resources accepted userData, metaData, and networkData secret references pointing to arbitrary namespaces. A user could configure a Metal3Machine to reference secrets in namespaces they do not have access to, and the controller would fetch and use those secrets. 2. Cross-namespace…

    Recommended action: Upgrade to 1.12.5 or 1.11.8 by release line, 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 →