Compromise a container
The adversary gains code execution in a workload container.
- Preconditions
- Vulnerable workload
- Required access
- Network.
- Potential evidence
- GuardDuty Runtime Monitoring
- Defensive controls
- Patching; image scanning
Attack scenario · Kubernetes & infrastructure
How can a container escape lead to AWS account compromise? A privileged container escapes to its node and uses the node’s IAM role, which is far more powerful than any single workload’s.
Attack path · 4 stages
Compromise a container
T1190
Escape to the node
T1611
Use the node IAM role
T1552.005
Abuse node permissions
T1525T1530
For leadership
Containers share the underlying server. If one container is allowed to run with elevated privileges or mount host paths, compromising it can mean compromising the server — and the cloud credentials the server holds. Node credentials are often broader than any application needs, because nodes pull images, manage networking and sometimes much more. This scenario shows why workload isolation and minimal node permissions matter even when individual applications are well-scoped. The fixes are mostly configuration — enforcing pod security standards, blocking pod access to node metadata and trimming node roles — and can be rolled out gradually without application changes.
For engineers
A pod running privileged, with hostPath "/" or host PID, escapes to the node (T1611). From the node, IMDS returns the node instance role credentials; if pods can reach IMDS directly (hop limit 2+), escape is not even required.
Fictional company: a logging DaemonSet runs privileged with hostPath mounts. The node role includes AmazonEC2ContainerRegistryPowerUser plus extra S3 permissions added for a past debugging task. IMDS hop limit is 2.
Interactive
Select a stage, or use the arrow keys, to see preconditions, evidence and controls.
The adversary gains code execution in a workload container.
| ID | Technique | Tactics (official) | Stages |
|---|---|---|---|
| T1190 | Exploit Public-Facing Application | Initial Access | 1 |
| T1611 | Escape to Host | Privilege Escalation | 2 |
| T1552.005 | Unsecured Credentials: Cloud Instance Metadata API | Credential Access | 3 |
| T1525 | Implant Internal Image | Persistence | 4 |
| T1530 | Data from Cloud Storage | Collection | 4 |
Technique names and tactic assignments come from the imported MITRE data. Mapping a stage to a technique is Securitain’s analysis.
Block privileged pods and host mounts outside a small, reviewed set of system namespaces.
Control: Restricted pod security settings · Kubernetes documentation
Prevent pods from reaching node credentials.
Control: Enforce IMDSv2 and limit metadata reachability · AWS documentation
Node role should only pull images and manage networking.
| Signal | Telemetry source | Notes |
|---|---|---|
| Container escape and privilege-escalation behaviour on nodes | GuardDuty Runtime Monitoring | — |
| Node role performing write actions (ECR push, IAM) | CloudTrail management events | — |
Telemetry only helps if it is enabled before the incident and someone acts on it. Listing a signal here does not mean it is collected or monitored in your environment.
For leadership
No financial loss estimates are given; impact depends on the data, contracts and regulation involved.
MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation. ATT&CK data © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation (ATT&CK v20.1). Securitain is not affiliated with or endorsed by MITRE. Explanations, scenarios and control mappings on this page are Securitain’s own analysis. Sources and licensing
Stay in the loop