If an attacker can write to the filesystem of a container k8s cluster container, they can plant an exec credential plugin in /etc/kubernetes
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.5.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The software affected is Container, a tool for running Linux containers and Kubernetes clusters on macOS, and its k8s cluster feature. A local attacker who can write to files inside a container's Kubernetes cluster can plant a malicious credential plugin that runs as the macOS host user when the kubeconfig is pulled to the host and used with kubectl, allowing arbitrary command execution on the host.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
If an attacker can write to the filesystem of a container k8s cluster container, they can plant an exec credential plugin in /etc/kubernetes/admin.conf. kubectl will run that plugin as the macOS host user the next time someone pulls the cluster's kubeconfig onto the host with container k8s write-config or create and then runs kubectl against it — turning filesystem access inside an untrusted Linux container into arbitrary command execution on the host. This vulnerability is addressed in Container version 1.5.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Apple Container
fixed in 1.5.0