fix: pin trivy-action by SHA to prevent supply chain attacks#80
Merged
Conversation
Pin aquasecurity/trivy-action from tag reference (v0.35.0) to its immutable commit SHA (57a97c7e7821a5776cebc9bb87c984fa69cba8f1). Tag references are mutable and can be moved to point at malicious commits. SHA pinning ensures the exact verified code is always used, mitigating supply chain attack vectors like the one disclosed in the tj-actions/changed-files incident. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
|
Note Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported. |
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
aquasecurity/trivy-actionfrom mutable tag reference (@0.35.0) to immutable commit SHA (@57a97c7e7821a5776cebc9bb87c984fa69cba8f1 # v0.35.0)Why
Git tags are mutable -- a repository maintainer (or attacker with write access) can move a tag to point at a different commit. This is exactly what happened in the tj-actions/changed-files supply chain attack (March 2025), where attackers rewrote tags to inject malicious code into CI pipelines.
SHA-pinning ensures the workflow always runs the exact verified code, regardless of tag mutations. The version comment (
# v0.35.0) preserves readability for Dependabot/Renovate updates.Test plan