Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS "Managed Policy Allows "sts:AssumeRole" For All Resources" misinterprets permissions boundaries #1666

Open
rdegraaf-ncc3 opened this issue Aug 29, 2024 · 0 comments
Labels
bug Something isn't working potential Unconfirmed issue

Comments

@rdegraaf-ncc3
Copy link
Contributor

Describe the bug

The AWS rule "IAM Principals With Access to sts:AssumeRole for Resource *" reported a number of target along the lines of the following:

* The role named `FooRole` through the policy `arn:aws:iam::123456789012:policy/Boundary`

Looking into the permissions of FooRole, its permission policies do not allow any STS permissions under any conditions. The "Boundary" permission policy does allow sts:* for the resource *, but it is attached as a permissions boundary, not as a permission policy. As a permissions boundary, it does not grant any permissions; it only limits the permissions that can be granted by attached permission policies. It appears that ScoutSuite is treating the permission boundary as a normal permission policy.

@rdegraaf-ncc3 rdegraaf-ncc3 added bug Something isn't working potential Unconfirmed issue labels Aug 29, 2024
@rdegraaf-ncc3 rdegraaf-ncc3 changed the title AWS "IAM Principals With Access to sts:AssumeRole for Resource *" misinterprets permissions boundaries AWS "Managed Policy Allows "sts:AssumeRole" For All Resources" misinterprets permissions boundaries Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working potential Unconfirmed issue
Projects
None yet
Development

No branches or pull requests

1 participant