-
Notifications
You must be signed in to change notification settings - Fork 63
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
internal/vulncheck: emit OSVs in their raw form asap
We omit raw unfiltered OSVs the moment we fetch them from the database. In practice, findings will be linked to a proper subset of these, making more explicit govulncheck strengths of taking into account: - module versions - platform information - symbols and their reachability via call graph Change-Id: I3330535938ac037ccc9fae84562fa4270fd00d0e Reviewed-on: https://go-review.googlesource.com/c/vuln/+/538788 LUCI-TryBot-Result: Go LUCI <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Maceo Thompson <[email protected]> Run-TryBot: Zvonimir Pavlinovic <[email protected]>
- Loading branch information
1 parent
b7bbfa0
commit aca0fd4
Showing
10 changed files
with
930 additions
and
34 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
aca0fd4
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.
Doesn't this change make it impossible to determine the "their reachability via call graph" of that last bullet item from just the JSON output? (refs tianon/gosu#144)
aca0fd4
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.
Emitted osvs are the osvs in the vulnerability database defined for the module dependencies of your program, regardless of the versions at which you are using them. Emitted osvs are not findings.
Also note that the content in the JSON output is not guaranteed to have any particular order, especially in test files.
aca0fd4
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.
So, I was previously using the JSON format to filter findings I know to be not applicable, which isn't supported by
govulncheck
yet -- is there a recommended way to accomplish that instead? 😇(Do I need to parse the
sarif
format or something instead?)aca0fd4
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've left a comment on your original issue and will leave it here. It seems you are not looking at govulncheck Findings at all. These contain what you want and the comments there explain how to perform filtering, which should be straightforward.