-
Notifications
You must be signed in to change notification settings - Fork 35
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Problem
The current vulnerability check utilized by the oci-factory is giving a lot of false positives, mainly as it does not check whether the code that contains the vulnerability is ever imported or called.
What happens at the moment is that we, every time a vulnerability is flagged, have to run govulncheck
against the project to see whether the CVE is actually affecting us or not and add it to trivyignore
if it isn't. A downside of this is that if the upstream ever starts to include the vulnerable code, it is already ignored and won't be flagged.
Additionally, we have no way of flagging trivyignores
for specific rock versions - only globally, which is a huge drawback.
Suggested solution
This requires a two step solution:
trivyignore
files per rock version, or a way to pin ignores to version ranges.- When a go project is detected,
govulncheck
should be run, either as well or in place of trivy, and anything not present in both cve lists get excluded.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working