Root access via shared builder SSH password
Published Oct 15, 2024 · Updated Oct 16, 2024
Hard-coded credentials in Kubernetes Image Builder 0.1.37 and earlier allow attackers to gain root access to build VMs. The Nutanix, OVA, QEMU, and raw provider workflows assign the builder SSH account a shared default password instead of a per-build random value. The attacker must reach the VM during image construction and modify it before the account is disabled; only clusters deployed from a modified image inherit the compromise.
Summary
What happened
Hard-coded credentials in Kubernetes Image Builder 0.1.37 and earlier allow attackers to gain root access to build VMs. The Nutanix, OVA, QEMU, and raw provider workflows assign the builder SSH account a shared default password instead of a per-build random value. The attacker must reach the VM during image construction and modify it before the account is disabled; only clusters deployed from a modified image inherit the compromise.
The record
- CVE
- CVE-2024-9594
- Published
- Oct 15, 2024
- Updated
- Oct 16, 2024
- Vendor
- Kubernetes
- Product
- Image Builder
- Classifications
- CWE-798, CAPEC-395, T1078.001
- Attack vector
- adjacent
- Privileges
- admin
Timeline
How it unfolded
- Oct 15, 2024CVE publishedPublication date reported by the CVE source.
- Oct 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.1.37
- Affected versionversion=0 <0.1.38
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo