English
Español
Français
Deutsch
日本語
한국어
العربيةPass role to HealthOmics
Can create a HealthOmics workflow with a role and run a task as it.
Grants escalation only in combination. All of these are needed together:
iam:PassRoleomics:CreateWorkflowomics:StartRuniam:PassRole can create a HealthOmics workflow with a role and run a task as it, but only when it is held together with omics:CreateWorkflow, omics:StartRun. Held together they reach administrator access.
Why it is dangerous
A principal holds iam:PassRole on the target role plus omics:CreateWorkflow and omics:StartRun, so it can create an AWS HealthOmics workflow whose task runs as the target role and start a run passing the target role as the execution role, the task executes with the target role's permissions and exfiltrates the target role's credentials (or calls AWS directly). Because the target role trusts omics.amazonaws.com the pass is accepted; if the target role is privileged this is full privilege escalation.
In MITRE ATT&CK terms this maps to T1648, Serverless Execution, under the privilege escalation tactic. AWS records it in CloudTrail as CreateWorkflow, StartRun. The call shows up in CloudTrail but blends into normal administration, so it needs a rule to stand out.
Detection
CreateWorkflowStartRunPrerequisites
Target role's trust policy must allow omics.amazonaws.com; an attacker-writable S3 bucket and a private ECR image the workflow task can run (HealthOmics requires private ECR images).
MITRE ATT&CK
T1648 · Serverless ExecutionTactic
Privilege Escalation
A control that would remove it: Remove iam:PassRole for this role or scope it with iam:PassedToService.
Whether to apply it depends on how the permission is used in your environment, so it is a business decision rather than an automatic fix. The same permission can be load-bearing in one account and pure risk in another.
Pathbreak confirms whether this path resolves in your account, ranks it against the others by how much it opens up, and uses your threat model and business context to show which paths are worth cutting.
Questions
What does iam:PassRole allow?
Can create a HealthOmics workflow with a role and run a task as it.
What else is needed for iam:PassRole to be dangerous?
It becomes an escalation only when held together with omics:CreateWorkflow, omics:StartRun. On its own it is not enough, which is what makes the combination easy to miss.
How is pass role to HealthOmics detected?
Watch for CreateWorkflow, StartRun in CloudTrail. The call shows up in CloudTrail but blends into normal administration, so it needs a rule to stand out.
How do you break this path?
A control that would remove it is: Remove iam:PassRole for this role or scope it with iam:PassedToService. Whether to apply it depends on how the permission is used in your account, so it is a business decision rather than an automatic fix.
Which MITRE ATT&CK technique is this?
T1648, Serverless Execution, under the privilege escalation tactic.
Related paths
References
Find this in your own account
We run a read-only scan of one AWS account and show you which of these paths exist, ranked by blast radius, with the change that breaks each one. First validated paths within the hour.