You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AWS IAM RolesAnywhere allows workloads outside AWS to assume IAM roles using X.509 certificates. But when trust policies aren't properly scoped, they can be abused for privilege escalation.
6
+
7
+
This policy lacks restrictions on which trust anchor or certificate attributes are allowed. As a result, any certificate tied to any trust anchor in the account can be used to assume this role.
8
+
9
+
```json
10
+
{
11
+
"Version": "2012-10-17",
12
+
"Statement": [
13
+
{
14
+
"Effect": "Allow",
15
+
"Principal": {
16
+
"Service": "rolesanywhere.amazonaws.com"
17
+
},
18
+
"Action": [
19
+
"sts:AssumeRole",
20
+
"sts:SetSourceIdentity",
21
+
"sts:TagSession"
22
+
]
23
+
}
24
+
]
25
+
}
26
+
27
+
```
28
+
29
+
To privesc, the `aws_signing_helper` is required from https://docs.aws.amazon.com/rolesanywhere/latest/userguide/credential-helper.html
30
+
31
+
Then using a valid certificate the attacker can pivot into the higher privilege role
0 commit comments