FKIE_CVE-2024-9594

Vulnerability from fkie_nvd - Published: 2024-10-15 21:15 - Updated: 2026-06-17 08:24
Severity
6.3 (Medium) - CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H
8.1 (High) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Summary
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.
References
jordan@liggitt.nethttps://github.com/kubernetes-sigs/image-builder/pull/1596Patch
jordan@liggitt.nethttps://github.com/kubernetes/kubernetes/issues/128007Issue Tracking
jordan@liggitt.nethttps://groups.google.com/g/kubernetes-security-announce/c/UKJG-oZogfA/m/Lu1hcnHmAQAJVendor Advisory
Impacted products
Vendor Product Version
kubernetes-sigs image_builder *
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Image Builder",
          "repo": "https://github.com/kubernetes-sigs/image-builder",
          "vendor": "Kubernetes",
          "versions": [
            {
              "lessThanOrEqual": "0.1.37",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "status": "unaffected",
              "version": "0.1.38"
            }
          ]
        }
      ],
      "source": "jordan@liggitt.net"
    },
    {
      "affectedData": [
        {
          "cpes": [
            "cpe:2.3:a:kubernetes:image_builder:*:*:*:*:*:*:*:*"
          ],
          "defaultStatus": "unknown",
          "product": "image_builder",
          "vendor": "kubernetes",
          "versions": [
            {
              "lessThan": "0.1.38",
              "status": "affected",
              "version": "0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
    }
  ],
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:kubernetes-sigs:image_builder:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "99A47BD9-7EEE-44AD-9D49-7740B2825053",
              "versionEndExcluding": "0.1.38",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "A security issue was discovered in the Kubernetes Image Builder versions \u003c= v0.1.37 where default credentials are enabled during the image build process\u00a0when 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."
    },
    {
      "lang": "es",
      "value": "Se descubri\u00f3 un problema de seguridad en las versiones de Kubernetes Image Builder \u0026lt;= v0.1.37, donde las credenciales predeterminadas se habilitan durante el proceso de creaci\u00f3n de im\u00e1genes cuando se utilizan los proveedores Nutanix, OVA, QEMU o raw. Las credenciales se pueden utilizar para obtener acceso ra\u00edz. Las credenciales se deshabilitan al finalizar el proceso de creaci\u00f3n de im\u00e1genes. Los cl\u00fasteres de Kubernetes solo se ven afectados si sus nodos utilizan im\u00e1genes de VM creadas a trav\u00e9s del proyecto Image Builder. Debido a que estas im\u00e1genes eran vulnerables durante el proceso de creaci\u00f3n de im\u00e1genes, solo se ven afectadas si un atacante pudo llegar a la VM donde se estaba creando la imagen y utiliz\u00f3 la vulnerabilidad para modificar la imagen en el momento en que se estaba creando la imagen."
    }
  ],
  "id": "CVE-2024-9594",
  "lastModified": "2026-06-17T08:24:53.340",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "ADJACENT_NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 6.3,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "HIGH",
          "scope": "UNCHANGED",
          "userInteraction": "REQUIRED",
          "vectorString": "CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 0.4,
        "impactScore": 5.9,
        "source": "jordan@liggitt.net",
        "type": "Secondary"
      },
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 8.1,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
          "version": "3.1"
        },
        "exploitabilityScore": 2.2,
        "impactScore": 5.9,
        "source": "nvd@nist.gov",
        "type": "Primary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2024-9594",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "total"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2024-10-16T16:20:46.180323Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2024-10-15T21:15:11.790",
  "references": [
    {
      "source": "jordan@liggitt.net",
      "tags": [
        "Patch"
      ],
      "url": "https://github.com/kubernetes-sigs/image-builder/pull/1596"
    },
    {
      "source": "jordan@liggitt.net",
      "tags": [
        "Issue Tracking"
      ],
      "url": "https://github.com/kubernetes/kubernetes/issues/128007"
    },
    {
      "source": "jordan@liggitt.net",
      "tags": [
        "Vendor Advisory"
      ],
      "url": "https://groups.google.com/g/kubernetes-security-announce/c/UKJG-oZogfA/m/Lu1hcnHmAQAJ"
    }
  ],
  "sourceIdentifier": "jordan@liggitt.net",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-798"
        }
      ],
      "source": "jordan@liggitt.net",
      "type": "Secondary"
    },
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-798"
        }
      ],
      "source": "nvd@nist.gov",
      "type": "Primary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.