-
Notifications
You must be signed in to change notification settings - Fork 2
Update aquasecurity/trivy-action digest to 76071ef #58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
479e72d
to
582fd00
Compare
582fd00
to
8409f3c
Compare
8409f3c
to
15c5cc7
Compare
15c5cc7
to
75f4c60
Compare
c646604
to
5431f6d
Compare
5431f6d
to
36026ea
Compare
6781142
to
36d571b
Compare
36d571b
to
ab9e6e2
Compare
ab9e6e2
to
4ada59e
Compare
Hi there 👋, @DryRunSecurity here, below is a summary of our analysis and findings.
Note 🟢 Risk threshold not exceeded. Change Summary (click to expand)The following is a summary of changes in this pull request made by me, your security buddy 🤖. Note that this summary is auto-generated and not meant to be a definitive list of security issues but rather a helpful summary from a security perspective. Summary: The code change in this GitHub Actions workflow is related to updating the version of the Trivy vulnerability scanner action used in the workflow. Trivy is a popular open-source tool for scanning container images and file systems for known vulnerabilities. The key changes in this pull request are the update of the Trivy action version from From an application security perspective, this change is positive as it ensures the workflow is using the latest version of the Trivy action, which may include bug fixes, performance improvements, or additional features. Keeping security tools up-to-date is an important aspect of maintaining a secure application. Additionally, the use of the Trivy vulnerability scanner and the integration with the GitHub Security tab are good security practices, as they help identify and track known vulnerabilities in the application's dependencies and container images, allowing the development team to address these issues and improve the overall security posture of the application. Files Changed:
Powered by DryRun Security |
4ada59e
to
280b1d7
Compare
280b1d7
to
7fae797
Compare
7fae797
to
450fba3
Compare
450fba3
to
5d1a46f
Compare
f840ee1
to
cb464d4
Compare
cb464d4
to
d6ac38f
Compare
d6ac38f
to
6f51e63
Compare
6f51e63
to
77ed95f
Compare
Stale pull request message |
77ed95f
to
ecf8051
Compare
ecf8051
to
5592aae
Compare
5592aae
to
fe137b6
Compare
fe137b6
to
f133fa8
Compare
f133fa8
to
7203823
Compare
7203823
to
02edd49
Compare
This pull request improves security by pinning the Trivy Action to a specific commit hash in the workflow, which prevents potential supply chain attacks and ensures reproducibility by using an immutable reference to the action's code.
|
Vulnerability | Supply Chain Dependency Pinning |
---|---|
Description | The workflow has been improved by pinning the Trivy Action to a specific commit hash, which is a positive security practice. By using a specific commit hash instead of a mutable tag, the workflow prevents potential supply chain attacks where an attacker could modify the action's code. This change ensures reproducibility and prevents unexpected code execution. The commit hash provides a fixed, immutable reference to the exact version of the action, mitigating risks associated with dynamic tag updates. |
scsctl/.github/workflows/trivy.yml
Lines 34 to 40 in 9ba9233
docker build -t docker.io/my-organization/my-app:${{ github.sha }} . | |
- name: Run Trivy vulnerability scanner | |
uses: aquasecurity/trivy-action@76071ef0d7ec797419534a183b498b4d6366cf37 | |
with: | |
image-ref: 'docker.io/my-organization/my-app:${{ github.sha }}' | |
format: 'template' |
All finding details can be found in the DryRun Security Dashboard.
02edd49
to
c48f90b
Compare
c48f90b
to
84c2163
Compare
84c2163
to
9ba9233
Compare
This PR contains the following updates:
7b7aa26
->76071ef
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.