wanderer/ PayloadsAllTheThings
1
0
Fork 0
mirror of https://github.com/swisskyrepo/PayloadsAllTheThings.git synced 2024-05-06 12:56:08 +02:00
Code Issues Releases Activity

Merge pull request #606 from hackprogrammatic/patch-1 

Update Cloud - AWS Pentest.md
This commit is contained in:
Swissky 2022-12-08 08:46:05 +01:00 committed by GitHub
parent 6709d543f4 749420fdd2
commit a1c5926f31
Signed by: GitHub
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Methodology and Resources/Cloud - AWS Pentest.md
View File

@ -746,7 +746,7 @@ The credential file is located in `~/.aws/credentials`
## Listing IAM access Keys
```
aws iam list-acess-keys
aws iam list-access-keys
```
## 1. Enumerating IAM users
@ -988,7 +988,7 @@ aws s3 ls --profile example_profile
### Persistence & Backdooring
* Suppose we have two users, the user A has permissions to create Access Keys to user B, this misconfig allows us to create an access key for user B and persist our access.
#### Creating a new acess key for another user
#### Creating a new access key for another user
```
aws iam create-access-key --username example_username
@ -2284,7 +2284,7 @@ aws ec2 describe-network-acls
### Scenario
* There are 3 VPC's -> A,B,C
* A can acess B through peering and B access C. We can use VPC B as a peering pivot to acess VPC C from VPC A.
* A can access B through peering and B access C. We can use VPC B as a peering pivot to access VPC C from VPC A.
* The lateral movement can be done if we gather keys or other machines
* Always enumerate the subnets to see in which subnet we can access other VPC's