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
Copy file name to clipboardExpand all lines: content/aws/post_exploitation/aws_consoler.md
+2-1
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,8 @@ description: "Leverage stolen credentials to use the AWS Console."
7
7
Original Research: [Ian Williams](https://blog.netspi.com/gaining-aws-console-access-via-api-keys/)
8
8
Link to Tool: [GitHub](https://github.com/NetSPI/aws_consoler)
9
9
10
-
__Required IAM Permissions__: sts:GetFederationToken OR sts:AssumeRole.
10
+
!!! Note
11
+
It is a good idea to install AWS Consoler in a Docker container or other disposable environment. The dependencies on the project may affect your existing AWS CLI install.
11
12
12
13
When performing an AWS assessment you will likely encounter IAM Credentials. Traditionally, the majority of these that you would find would only be usable from the AWS CLI. Using a tool called [AWS Consoler](https://github.com/NetSPI/aws_consoler) you can create links that will allow you to access the AWS Console. In this example we will walk through gathering credentials and using those credentials along with Consoler to generate a Console link.
0 commit comments