Repository navigation
fix: prevent Azure setupRef command injection - #184
Merged
Merged
Conversation
fengmk2
marked this pull request as ready for review
October 8, 2026 03:42
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.
azure/setup-vp.ymlinsertedsetupRefdirectly into Bash and PowerShell scripts. A crafted value could execute commands on the agent.Both prepare steps now read
SETUP_VP_SETUP_REFfrom the environment and reject unsafe values before the bootstrap download. The allowed format supports release tags, branch paths, and commit SHAs.