Security PoC: pull_request_target code execution#3646
Closed
orihamama wants to merge 1 commit intogithub:mainfrom
Closed
Security PoC: pull_request_target code execution#3646orihamama wants to merge 1 commit intogithub:mainfrom
orihamama wants to merge 1 commit intogithub:mainfrom
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Security Research — Coordinated Disclosure
This PR demonstrates a security vulnerability in the
jekyll-preview.ymlworkflow.Issue: The workflow uses
pull_request_targetand checks out the PR author's fork code, then builds Jekyll from it. Jekyll plugins in_plugins/execute arbitrary Ruby during the build.Impact: Any GitHub user can achieve code execution on the runner with
pages:writeandid-token:writepermissions.This PR contains a benign PoC that only prints environment info (no destructive actions, no secret exfiltration).
I will be submitting a full report to GitHub's HackerOne bug bounty program.
— @orihamama