Update Trivy GitHub Action to v0.35.0#2031
Conversation
|
@shibd:Thanks for your contribution. For this PR, do we need to update docs? |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 521a4ceb3b
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| - name: Run Trivy vulnerability scanner | ||
| uses: aquasecurity/trivy-action@master | ||
| uses: aquasecurity/trivy-action@v0.35.0 |
There was a problem hiding this comment.
Pin Trivy action to a full commit SHA
Replacing @master with @v0.35.0 still leaves this workflow consuming a mutable third-party ref. GitHub’s secure-use docs say a full commit SHA is “the only way to use an action as an immutable release” and explicitly note that tags can be moved or deleted, so if Aqua retargets v0.35.0 (or their repo is compromised again) this PR job will execute different code than the release you reviewed. To actually remove the supply-chain exposure this change is addressing, pin the vetted v0.35.0 commit SHA instead.
Useful? React with 👍 / 👎.
Summary
aquasecurity/trivy-action@masterwithaquasecurity/trivy-action@v0.35.0masterref after the recent Trivy GitHub Action security incidentTesting