Repository navigation
harden docker workflow against CI injection attacks - #245
Merged
Merged
Conversation
- add permissions: contents: read, packages: write (least privilege)
- add event == 'push' guard to prevent workflow_run firing on PR events
- use env: mapping for head_branch instead of direct ${{ }} interpolation in shell
steps.tags.outputs.* values derived from head_branch were still
interpolated via ${{ }} in run: blocks. Now passed via env:.
This was referenced Mar 11, 2026
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
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.
Summary
permissions: contents: read, packages: write(least privilege)github.event.workflow_run.event == 'push'guard to prevent Docker builds from firing on PR-triggered CI completions${{ github.event.workflow_run.head_branch }}interpolation inrun:blocks withenv:variable mapping to prevent shell injection via attacker-controlled branch namesContext: https://www.stepsecurity.io/blog/hackerbot-claw-github-actions-exploitation