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

feat: use ghsa to improve matching for cpes #811

Closed
cpendery opened this issue Jun 27, 2022 · 4 comments · Fixed by #1412
Closed

feat: use ghsa to improve matching for cpes #811

cpendery opened this issue Jun 27, 2022 · 4 comments · Fixed by #1412
Labels
enhancement New feature or request

Comments

@cpendery
Copy link
Contributor

Another thing which might potentially be useful (and should probably be configurable on individual ecosystem matcher level) could be if we find an NVD match and that CVE has a GHSA for another ecosystem (and the eocsystem we're matching for is supported by GitHub) we filter it out. Hopefully that makes sense but if not I can try and explain it better.

Originally posted by @westonsteimel in #390 (comment)

@cpendery
Copy link
Contributor Author

I wanted to keep track of this idea when my pr closes its source issue in order to investigate in the future

@westonsteimel
Copy link
Contributor

westonsteimel commented Jun 28, 2022

Yes, so I'm already working on a feature for this internally. It will be configurable to define some hierarchy of namespaces which should be considered authoritative. I'll let you know when I'm ready with it so you can evaluate.

@spiffcs
Copy link
Contributor

spiffcs commented Jun 28, 2022

Thanks @westonsteimel!

@cpendery
Copy link
Contributor Author

Amazing! @westonsteimel I skimmed the v4 schema and I'm super excited for it too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants