Adversaries may deploy a container into an environment to facilitate execution or evade defenses. In some cases, adversaries may deploy a new container to execute processes associated with a particular image or deployment, such as processes that execute or download malware. In others, an adversary may deploy a new container configured without network rules, user limitations, etc. to bypass existing defenses within the environment. In Kubernetes environments, an adversary may attempt to deploy a privileged or vulnerable container into a specific node in order to Escape to Host and access other containers running on the node.1 Containers can be deployed by various means, such as via Docker's <code>create</code> and <code>start</code> APIs or via a web application such as the Kubernetes dashboard or Kubeflow.234 In Kubernetes environments, containers may be deployed through workloads such as ReplicaSets or DaemonSets, which can allow containers to be deployed across multiple nodes.5 Adversaries may deploy containers based on retrieved or built malicious images or from benign images that download and execute malicious payloads at runtime.6
- AppSecco Kubernetes Namespace Breakout 2020
- Docker Container
- Kubernetes Dashboard
- Kubeflow Pipelines
- Kubernetes Workload Management
- Aqua Build Images on Hosts
Groups using this technique
| Group | Name | Country |
|---|---|---|
| grp_g1056 | TeamPCP | — |
| grp_g1045 | Salt Typhoon | — |
| grp_g0139 | TeamTNT | — |
Claims
No public claim points at this technique yet.
Auto-ingested and not human-reviewed; confidence and validity read by citation.