Add SSRF to GCP metadata write-up to Writeups - #8
Open
MBK-fr wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds one SSRF write-up to the Writeups section: a server side request forgery escalated to the GCP metadata service, abusing the gopher:// scheme to steal a service account token and pivot, with reproducible proof of exploitation.
Write-up: SSRF to GCP Metadata: Stealing a Service Account Token With gopher://
https://dark-moon.org/blog/ssrf-gcp-metadata-token-theft/
Disclosure: I contribute to the project behind this write-up (Darkmoon, an open source pentest platform). I propose it because it fits the SSRF Writeups scope of this list. If you consider it out of scope I will gladly adjust or withdraw the PR.