Skip to content
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

TODO: Need mitigation description for "Include a vulnerable dependency" threat #1183

Open
lehors opened this issue Oct 9, 2024 · 2 comments
Labels

Comments

@lehors
Copy link
Member

lehors commented Oct 9, 2024

No description provided.

@lehors lehors added the slsa 1.1 label Oct 9, 2024
@TomHennen
Copy link
Contributor

I think the answer to this will be mostly the same as (G). I'll wait until #1190 is merged before making a proposal.

@michaelwinser
Copy link

This starts with admission control over the full dependency graph, not just those explicitly mentioned in a project's dependencies.

If the dependency inclusion is not declarative then static code analysis might be required to even detect the inclusion of the vulnerable code. The risk of copy-paste inclusion of vulnerabilities, especially from bad sample code is significant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🆕 New
Development

No branches or pull requests

3 participants