Adversaries may create or modify container or container cluster management tools that run as daemons, agents, or services on individual hosts. These include software for creating and managing individual containers, such as Docker and Podman, as well as container cluster node-level agents such as kubelet. By modifying these services, an adversary may be able to achieve persistence or escalate their privileges on a host. For example, by using the `docker run` or `podman run` command with the `restart=always` directive, a container can be configured to persistently restart on the host.1 A user with access to the (rootful) docker command may also be able to escalate their privileges on the host.2 In Kubernetes environments, DaemonSets allow an adversary to persistently Deploy Containers on all nodes, including ones added later to the cluster.34 Pods can also be deployed to specific nodes using the `nodeSelector` or `nodeName` fields in the pod spec.56 Note that containers can also be configured to run as Systemd Services.78
- AquaSec TeamTNT 2023
- GTFOBins Docker
- Aquasec Kubernetes Attack 2023
- Kubernetes DaemonSet
- Kubernetes Assigning Pods to Nodes
- AppSecco Kubernetes Namespace Breakout 2020
- Podman Systemd
- Docker Systemd
Groups using this technique
| Group | Name | Country |
|---|---|---|
| grp_g1045 | Salt Typhoon | — |
Claims
No public claim points at this technique yet.
Auto-ingested and not human-reviewed; confidence and validity read by citation.