3 ms·
I'm trying to understand what the issue here was. Did they publicly expose the kubelet port on the internet?
by alpb 9y ago
I'm trying to understand what the issue here was. Did they publicly expose the kubelet port on the internet?
- jc_sec 9y agoYep. The kubelet ports were exposed. From the article: As it turns out, our coworker’s server was also publicly exposing the kubelet ports (tcp 10250, tcp 10255). Although the problem here was obvious, it should raise some questions about your own Kubernetes deployment, as it did for us.
- jc_sec 9y agoTry a quick nmap scan on an AWS or Google IP range for tcp port 10250 to see some scary results.