Skip to main content

Mom, I'm in a Pod! Leveraging DNS to leak cluster intel

Feb 5, 2027 — 02:30 pm - 3:20 PM
Cloud

You need to register and log in to access this functionality
Mom, I'm in a Pod! Leveraging DNS to leak cluster intel

Abstract

During a penetration test, following the exploitation of an RCE type vulnerability on an exposed application, you find yourself in a Pod of a Kubernetes cluster. The Pod in question has no rights on the cluster, and there is no way to escape from it. What to do in this situation? First step would be to scan for other Pods and Services to exploit, but a cluster can contain millions of internal IP addresses, using a tool like nmap would take too much time and be unreliable. Moreover, a hardened cluster will block network interactions with NetworkPolicies, meaning that some workloads may be invisible from the compromised Pod. However, DNS service is always accessible, ensuring that a Pod can resolve other Services it might depend on, such as database, cache service or API. How can we leverage DNS to enumerate almost all the workloads running on a Kubernetes Cluster?

Speaker

Suggested sessions