Skip to content

← Public intelligence

Go package

github.com/kubernetes-sigs/image-builder

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

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

  1. Critical, CVSS 9.3GoPublished

    VM images built with Image Builder and Proxmox provider use default credentials in github.com/kubernetes-sigs/image-builder

    CVE-2024-9486 · GHSA-9224-ggvw-wh7v

    Affected
    • Go github.com/kubernetes-sigs/image-builder < 0.1.38
    Fixed in
    0.1.38· Vendor fix available
    Issue
    A security issue was discovered in the Kubernetes Image Builder versions <= v0.1.37 where default credentials are enabled during the image build process. Virtual machine images built using the Proxmox provider do not disable these default credentials, and nodes using the resulting images may be accessible via these default credentials. The credentials can be used to gain root access. Kubernetes clusters are only affected if their nodes use VM images created via the Image Builder project with its Proxmox provider.

    Recommended action: Upgrade to 0.1.38 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 →
  2. Medium, CVSS 5.4GoPublished

    VM images built with Image Builder with some providers use default credentials during builds in github.com/kubernetes-sigs/image-builder

    CVE-2024-9594 · GHSA-8jpg-62jc-hwhr

    Affected
    • Go github.com/kubernetes-sigs/image-builder < 0.1.38
    Fixed in
    0.1.38· Vendor fix available
    Issue
    A security issue was discovered in the Kubernetes Image Builder versions <= v0.1.37 where default credentials are enabled during the image build process when using the Nutanix, OVA, QEMU or raw providers. The credentials can be used to gain root access. The credentials are disabled at the conclusion of the image build process. Kubernetes clusters are only affected if their nodes use VM images created via the Image Builder project. Because these images were vulnerable during the image build process, they are affected only if an attacker was able to reach the VM where the image build was happening and used the vulnerability to modify the image at the time the image build was occurring.

    Recommended action: Upgrade to 0.1.38 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 →