Skip to content
StrikeOps

Privileged Containers and Host Access

HighTypical severity Containers, CI/CD and source codeCWE-250ATT&CK T1611

01Description

Containers were configured to run as privileged, with host namespaces, dangerous capabilities or sensitive host paths mounted.

02Impact

A compromise of the application inside such a container can escape to the underlying host and from there reach other workloads and cluster credentials.

03Severity

Typically

High

Typically High. High where a compromised container can reach the host. Medium if the container is privileged but runs only trusted, internal code.

04How to verify

  1. 1Review pod and container security contexts for privileged, hostPID, hostNetwork and added capabilities.
  2. 2Review host path mounts.
  3. 3Check whether Pod Security Admission or a policy engine enforces restrictions.

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. 1Remove privileged mode, host namespaces and unnecessary capabilities.
  2. 2Run containers as non-root with read-only file systems.
  3. 3Enforce the Pod Security 'restricted' standard or equivalent policies.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo