Last updated
Learn & practice AWS Hacking:HackTricks Training AWS Red Team Expert (ARTE) Learn & practice GCP Hacking: HackTricks Training GCP Red Team Expert (GRTE)
For more information about Cloud Run check:
GCP - Cloud Run Enum
run.services.create , iam.serviceAccounts.actAs, run.routes.invokeAn attacker with these permissions to create a run service running arbitrary code (arbitrary Docker container), attach a Service Account to it, and make the code exfiltrate the Service Account token from the metadata.
An exploit script for this method can be found here and the Docker image can be found here.
Note that when using gcloud run deploy instead of just creating the service it needs the update permission. Check an example here.
run.services.update , iam.serviceAccounts.actAsLike the previous one but updating a service:
run.services.setIamPolicyGive yourself previous permissions over cloud Run.
run.jobs.create, run.jobs.run, iam.serviceaccounts.actAs,(run.jobs.get)Launch a job with a reverse shell to steal the service account indicated in the command. You can find an exploit here.
run.jobs.update,run.jobs.run,iam.serviceaccounts.actAs,(run.jobs.get)Similar to the previous one it's possible to update a job and update the SA, the command and execute it:
run.jobs.setIamPolicyGive yourself the previous permissions over Cloud Jobs.
run.jobs.run, run.jobs.runWithOverrides, (run.jobs.get)Abuse the env variables of a job execution to execute arbitrary code and get a reverse shell to dump the contents of the container (source code) and access the SA inside the metadata:
Learn & practice AWS Hacking:HackTricks Training AWS Red Team Expert (ARTE) Learn & practice GCP Hacking: HackTricks Training GCP Red Team Expert (GRTE)
