Skip to content

Latest commit

 

History

History
68 lines (43 loc) · 3.49 KB

gcp-app-engine-post-exploitation.md

File metadata and controls

68 lines (43 loc) · 3.49 KB
Raw

GCP - App Engine Post Exploitation

Learn AWS hacking from zero to hero with htARTE (HackTricks AWS Red Team Expert)!

Other ways to support HackTricks:

App Engine

For information about App Engine check:

{% content-ref url="../gcp-services/gcp-app-engine-enum.md" %} gcp-app-engine-enum.md {% endcontent-ref %}

appengine.memcache.addKey | appengine.memcache.list | appengine.memcache.getKey | appengine.memcache.flush

With these permissions it's possible to:

  • Add a key
  • List keys
  • Get a key
  • Delete

{% hint style="danger" %} However, I couldn't find any way to access this information from the cli, only from the web console where you need to know the Key type and the Key name, of from the app engine running app.

If you know easier ways to use these permissions send a Pull Request! {% endhint %}

logging.views.access

With this permission it's possible to see the logs of the App:

gcloud app logs tail -s <name>

Read Source Code

The source code of all the versions and services are stored in the bucket with the name staging.<proj-id>.appspot.com. If you have write access over it you can read the source code and search for vulnerabilities and sensitive information.

Modify Source Code

Modify source code to steal credentials if they are being sent or perform a defacement web attack.

Learn AWS hacking from zero to hero with htARTE (HackTricks AWS Red Team Expert)!

Other ways to support HackTricks: