ci: add permissions and pin action SHAs in fuzz.yml#174
Open
Alb3e3 wants to merge 1 commit into
Open
Conversation
Add `permissions: read-all` at the workflow level to enforce least-privilege for all jobs, and pin all third-party action references to full commit SHAs to prevent supply-chain attacks via mutable version tags or branch names.
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.
Summary
The
fuzz.ymlCIFuzz workflow is missing a top-levelpermissionsdeclaration and references three actions by mutable tags/branch names, which are supply-chain risk vectors.Changes:
permissions: read-allat the workflow level (least-privilege default)google/oss-fuzz/.../build_fuzzers@master→ full commit SHAgoogle/oss-fuzz/.../run_fuzzers@master→ full commit SHAactions/upload-artifact@v1→ full commit SHAMutable references (
@master,@v1) allow a compromised upstream action to run arbitrary code in your CI. Pinning to a commit SHA ensures only the audited version runs, regardless of upstream changes.This patch is consistent with Google's own guidance on workflow security.