From 3cce6aa3409754fd14ce56a112f6d6eb16d73f90 Mon Sep 17 00:00:00 2001 From: Carlos Polop Date: Fri, 23 Oct 2026 05:00:07 +0200 Subject: [PATCH] Fix ECS privileged task route with scoped registration grants --- src/privilege-escalation-paths/aws/ecs.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/privilege-escalation-paths/aws/ecs.yaml b/src/privilege-escalation-paths/aws/ecs.yaml index e9884d5f1b..1f29eec5d6 100644 --- a/src/privilege-escalation-paths/aws/ecs.yaml +++ b/src/privilege-escalation-paths/aws/ecs.yaml @@ -228,9 +228,9 @@ source: src/pentesting-cloud/aws-security/aws-privilege-escalation/aws-ecs-privesc/README.md#ecsregistertaskdefinition-and-a-task-launching-action source_revision: 171e422299 summary: The source can obtain the privileges of the container-instance role and of task roles of tasks co-located on EC2 container instances by running a privileged/host-mounted container it controls. + # The native precondition checks registration on the generated task-definition family. requires: - all_of: - - action: ecs:RegisterTaskDefinition + all_of: [] source_kind: [aws_user, aws_role] target: kind: aws_role