Exposed Docker APIs Enable Container Breakouts, DDoS Malware, and Host Compromise
Attack Surface Exposure · 3 sources · Updated 3mo ago · First seen Dec 21, 2021

Attackers have been abusing improperly exposed Docker daemon APIs, especially unauthenticated services on port 2375, to take control of running containers and deploy malware. One documented campaign used the Dofloo (AESDDoS) Trojan to enumerate containers and run malicious payloads with Docker commands, giving operators DDoS capability, host profiling data, and a foothold for follow-on activity such as cryptojacking or broader system compromise.
Public tooling has also lowered the barrier to exploiting these weaknesses. The BOtB container assessment tool demonstrates how exposed Docker daemons, privileged container configurations, Kubernetes service account exposure, metadata service access, Linux kernel keyring leakage, and even runc escape flaw CVE-2019-5736 can be used to break out of containers or extract secrets in CI/CD and live environments. Docker’s guidance recommends protecting the daemon socket and restricting remote API access to trusted systems, underscoring that exposed or misconfigured container management interfaces can quickly turn a single container issue into host-level compromise.


