Docker daemon exposed on the network
The Docker daemon exposed over TCP (classically port 2375, unencrypted) with no authentication hands full control of the host to anyone who can connect — Docker runs as root.
Why it matters
Anyone reaching the Docker API can start a privileged container that mounts the host filesystem and takes over the machine. It's one of the most-scanned exposures on the internet.
There is almost never a good reason to bind the Docker socket to a public interface.
How to check for it
- Check for '-H tcp://0.0.0.0:2375' (or 2376) in the dockerd flags or /etc/docker/daemon.json ('hosts').
- From outside, a connection to port 2375/2376 that answers is the problem.
How to fix it
- Remove the TCP socket; use the local unix socket (/var/run/docker.sock) only.
- If you truly need remote access, use TLS mutual auth on 2376 and a firewall that limits the source — never plain 2375.
SkyShield checks this automatically
Connect your AWS, Cloudflare, GitHub, GitLab, Hetzner or DigitalOcean account read-only and SkyShield flags this across every account and region, with the fix in plain words — alongside the agent that watches your servers. Start free.