Skip to content
StrikeOps

Docker Socket Exposed

CriticalTypical severity Containers, CI/CD and source codeCWE-284ATT&CK T1610

01Description

The Docker socket was mounted into containers, or the Docker remote API was exposed on the network without TLS authentication.

02Impact

Anyone who can talk to the Docker daemon can start a privileged container that mounts the host file system, gaining root on the host.

03Severity

Typically

Critical

Typically Critical. Critical, as access to the Docker socket or an unauthenticated Docker API is equivalent to root on the host.

04How to verify

  1. 1Check for /var/run/docker.sock mounts in container configurations.
  2. 2Scan for the Docker API on TCP 2375 and 2376.
  3. 3Confirm whether unauthenticated requests are accepted.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Do not mount the Docker socket into application containers.
  2. 2Never expose the Docker API without mutual TLS, and preferably not on the network at all.
  3. 3Use rootless container runtimes where possible.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo