Source URL: https://www.theregister.com/2024/10/16/critical_kubernetes_image_builder_bug/
Source: The Register
Title: Critical default credential bug in Kubernetes Image Builder allows SSH root access
Feedly Summary: It’s called leaving the door wide open – especially in Proxmox
A critical bug in Kubernetes Image Builder could allow unauthorized SSH access to virtual machines (VMs) due to default credentials being enabled during the image build process.…
AI Summary and Description: Yes
Summary: The text discusses a critical vulnerability in Kubernetes Image Builder that could allow unauthorized SSH access to virtual machines due to default credentials. It highlights the risks associated with VM images created using specific providers and provides insights into severity ratings and mitigation measures.
Detailed Description:
The text addresses a significant security vulnerability identified in Kubernetes Image Builder, specifically affecting the building of virtual machine (VM) images with default credentials, which poses serious security threats. Here are the key points:
– **Vulnerability Overview**:
– The vulnerability in Kubernetes Image Builder allows unauthorized SSH access to VMs when default credentials remain enabled during the image building process.
– This flaw is tracked under CVE-2024-9486, which has been assigned a critical 9.8 out of 10 CVSS severity rating.
– **Affected Providers**:
– Images built with the Proxmox provider are most severely impacted.
– Other providers affected include Nutanix, OVA, QEMU, and raw providers, but the associated risk is lower (6.3 CVSS rating) under a separate CVE identifier: CVE-2024-9594.
– **Exploitation Details**:
– Successful exploitation of CVE-2024-9594 would enable an attacker to gain root access but requires proximity to the VM during the image build.
– Exploitation likelihood is reduced by certain providers disabling default credentials at the end of the image build process.
– **Mitigation and Remediation**:
– Users are advised to upgrade to Image Builder version 0.1.38 or later, which implements a randomly generated password during the build process and disables the builder account afterward.
– After upgrading, redeploying any affected VM images is necessary.
– A temporary workaround prior to upgrading involves disabling the builder account to mitigate risks.
– **Responsible Disclosure**:
– The bug was reported by Nicolai Rybnikar from Rybnikar Enterprises, emphasizing the importance of reporting security vulnerabilities responsibly.
This analysis is particularly relevant for professionals in infrastructure security, cloud computing, and those managing Kubernetes environments, ensuring the adherence to security best practices and vulnerability management.