hunt-k8s

Detect Kubernetes and Docker security misconfigurations and privilege escalation paths.

1.1k|191|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/uphiago/recon-skills --skill hunt-k8s-uphiago
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-k8s
Source: https://github.com/uphiago/recon-skills/tree/main/redteam/hunt-k8s
Command: npx skills add https://github.com/uphiago/recon-skills --skill hunt-k8s-uphiago

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, error-prone work of identifying high-impact Kubernetes and Docker security misconfigurations, unpatched CVEs, and privilege escalation paths that lead to full cluster or host compromise during authorized penetration testing of containerized infrastructure.

Core Features & Use Cases

  • Comprehensive K8s/Docker Enumeration: Fingerprints common Kubernetes and container management ports, detects anonymous API access, kubelet RCE vectors, unauthenticated etcd access, docker.sock exposure, and runc container escape vulnerabilities.
  • Validated Impact Proof: Includes out-of-band confirmation gates, false positive killers, and step-by-step validation checklists to ensure findings are accurate and reportable, avoiding common misconfigurations like conflating read-only kubelet 10255 with exploitable 10250.
  • Use Case: A red teamer assessing a cloud-native target can use this Skill to systematically validate anonymous API admin access, confirm kubelet /run RCE, and dump unencrypted etcd secrets without manual trial and error or false positive reporting.

Quick Start

Use the hunt-k8s skill to scan a target for exposed Kubernetes and Docker services, validate critical misconfigurations, and confirm RCE or credential leak vulnerabilities for your authorized penetration test.

Frequently Asked Questions about hunt-k8s

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find Kubernetes privilege escalation paths during a penetration test?

To find Kubernetes privilege escalation paths, you can scan for anonymous API admin access, exploitable kubelet RCE ports, and unauthenticated etcd access to identify routes for full cluster compromise.

What is the difference between read-only kubelet 10255 and exploitable kubelet 10250?

The difference is that read-only kubelet port 10255 provides non-exploitable data, while port 10250 exposes /run command execution vectors that allow remote code execution when misconfigured.

How can I validate docker.sock exposure for host escape vulnerabilities?

You validate docker.sock exposure by confirming socket access and interacting with the Docker API to spawn a privileged container, proving you can mount the host filesystem and achieve host escape.

Does this approach detect runc container escape vulnerabilities?

Yes, it detects runc container escape vulnerabilities by hunting for unpatched CVEs and specific misconfigurations in containerized environments that allow breaking out of the container sandbox to access the host.

What is the best way to prevent false positives when scanning for kubelet RCE?

The best way to prevent false positives when scanning for kubelet RCE is to use out-of-band confirmation gates and validation checklists that verify actual command execution rather than assuming port exposure alone equals vulnerability.

Can I dump unencrypted etcd secrets without prior cluster authentication?

You can dump unencrypted etcd secrets without prior cluster authentication if the etcd service exposes unauthenticated access, allowing direct database reads to extract sensitive credentials and cluster configuration data.