-
Notifications
You must be signed in to change notification settings - Fork 95
feat: Govulncheck source call analysis enricher #1555
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
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Return error instead of logging a warning
…running system req
de49305 to
ea5797d
Compare
enricher/enricher.go
Outdated
| EnricherOrder = []string{ | ||
| "reachability/java", | ||
| "vulnmatch/osvdev", | ||
| "reachability/govcsource", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how we order the enrichers in this list?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The govcsoruce needs the output from the initial vulnerability match in osvdev, so it has to happen after vulnerability matching.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you add a comment with this reason? and does that mean we need to specify vulnmatch/osvdev as one of the required plugins?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could also get vulns from our internal matcher plugin (plus theoretically detectors that might find specific vulns in Go binaries, though we don't have any atm) so I'd rather not specify vulnmatch/osvdev
| // If there is symbol information, then analysis has been performed, and | ||
| // code does not import the vulnerable package, so definitely not called |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel this comment is a bit hard to understand - can you rephrase it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rephrased it, PTAL!
Fork of #1208