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

x/vulndb: add fix version to reports when it becomes available #56334

Open
zpavlinovic opened this issue Oct 19, 2022 · 0 comments
Open

x/vulndb: add fix version to reports when it becomes available #56334

zpavlinovic opened this issue Oct 19, 2022 · 0 comments
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. vulncheck or vulndb Issues for the x/vuln or x/vulndb repo
Milestone

Comments

@zpavlinovic
Copy link
Contributor

If a vulnerability in a new report still does not have a fix, how do we include the fix information when and if it becomes available?

For std vulnerabilities this seems to be less of a problem since fixes have to go through the Go team.

For third party vulnerabilities, the story is less clear. Few options:

  • have a specific supression tag. This tag would not indicate that we should not report vulnerability, yet it will serve as a designation for which reports might need more info. We can then automatically and periodically go through such reports and, if they have a link to a GH issue, see if the issue is closed. If so, manually add the fix information.

  • perhaps we can hook to changes to Github advisories and if those changes mention fix info, we can add that info to the respective report.

@zpavlinovic zpavlinovic added the vulncheck or vulndb Issues for the x/vuln or x/vulndb repo label Oct 19, 2022
@zpavlinovic zpavlinovic added this to the Unplanned milestone Oct 19, 2022
@zpavlinovic zpavlinovic changed the title x/vulndb: add fix version when they become unavailable x/vulndb: add fix version to reports when it becomes available Oct 19, 2022
@dr2chase dr2chase added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Oct 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. vulncheck or vulndb Issues for the x/vuln or x/vulndb repo
Projects
None yet
Development

No branches or pull requests

2 participants