-
Notifications
You must be signed in to change notification settings - Fork 0
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
[Scorecard:Docker-Deps]: Docker dependencies not pinned #21
Comments
Re-opening this issue as scorecard reported the following issues:
Please let me know if you have questions. |
Re-opening this issue as scorecard reported the following issues:
Please let me know if you have questions. |
Re-opening this issue as scorecard reported the following issues:
Please let me know if you have questions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi team,
I ran OSSF's scorecard on your repo and it reported the following non-pinned docker dependencies:
In light of recent supply chain attacks like codecov, it would be useful to pin the dependencies by hash.
Pinning by version or any floating tag does not protect sufficiently, since it still allows attackers to update the dependencies if they can compromise a project.
@laurentsimon @laurentsimon2 FYI
How to fix
The fix is to use a hash to pin the dependencies. You can find an example here.
To find the hash corresponding to your dependency, run:
Updates remain feasible. Project owners usually enable github's dependabot through this settings. Dependabot will automatically
create PRs that you can review, accept or reject when new versions of your dependencies become available.
It is recommended to accept dependabot PRs regularly to receive security patches.
Several projects are taking steps to address the same issue, e.g. envoy proxy.
Please let me know if you have any questions.
The text was updated successfully, but these errors were encountered: