Kubernetes has finally hit the worst milestone: their first major security flaw. This vulnerability allows any user to escalate their administrative privileges and attack any container running on the same pod. Even worse, there’s no simple way to tell if you’ve been affected.
Grim news from Red Hat – Kubernetes has identified its first major security flaw. This vulnerability affecting Kubernetes 1.10 and higher was publicly disclosed on GitHub last week. Basically, the flaw allows any user to escalate their privileges to access administrative controls through the Kubernetes API server.
With this, they can create requests authenticated by Kubernetes’ own TLS credentials and mess with any container running on the same pod. While there’s a patch up already, it looks like this flaw is going to cause some pretty significant soul searching (and log searching). Kubernetes is one of the most popular open source projects today; it’s estimated that around 70% of all enterprises have adopted Kubernetes containers.
With such a large number of targets, it’s likely someone has already been hit. So, let’s get into the details and what this means for developers.