grte-mightocho #193
Merged
grte-mightocho #193
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
Includes direct gcloud command descriptioon to exploit this permission.
### `cloudbuild.builds.update` Currently this permission is listed to **only** be able to be used to use the api method `builds.cancel()` which cannot be abused to change the parameters of an ongoing build References: - https://cloud.google.com/build/docs/iam-roles-permissions#permissions - https://cloud.google.com/build/docs/api/reference/rest/v1/projects.builds/cancel
Collaborator
|
Nice one @hasshido ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Hi @carlospolop !
While doing GRTE I noticed a couple things that could be updated/improved here:
There's a much quicker way to abuse
cloudbuild.builds.create, iam.serviceAccounts.actAs. As of today, there's no need to use the linked scripts, as it is possible to trigger the build with the inline YAML directly through thegcloudcli.After investigating a bit more about
cloudbuild.builds.update, I saw on the gcloud docs that the only api permission it seems to give right now is to allow cancelling builds, which wouldn't allow for privilege escalation at the moment. For that reason, I'd suggest to remove it from the page to reduce noise and confusion.builds.cancel()API call.PS: If you do not consider this to be up-to-standard regarding the exam points, just let me know so I can keep that into consideration to make extra PRs 👍
I just thought this would be a nice update ^_^. Have a nice day!