What problem does it solve?
During authorized penetration tests, Docker Registry services on port 5000 are often misconfigured with unauthenticated access, weak basic auth, or open push permissions, yet testers frequently miss these issues because the registry is just an HTTP API. This Skill provides a structured methodology to enumerate, exploit, and prove Docker Registry exposures.
Core Features & Use Cases
- Registry Enumeration: Fingerprint the /v2/ API, determine HTTP vs HTTPS, and list repositories via /v2/_catalog with or without credentials.
- Secret Extraction from Image Layers: Download and unpack blobs to recover source code, .env files, configs, and credentials baked into image layers.
- Supply-Chain Backdoor Testing: With write access, push poisoned images (e.g., WordPress webshell or SSH images) to demonstrate downstream impact.
- Use Case: During an authorized engagement, nmap shows 5000/tcp open as a Docker Registry; you confirm unauthenticated catalog access, pull the wordpress image, and extract wp-config.php database credentials from its layers.
Quick Start
Ask the AI to enumerate the Docker Registry at the target IP on port 5000 and check whether /v2/_catalog is accessible without authentication.