-
Notifications
You must be signed in to change notification settings - Fork 190
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
Visibility of curl CVEs without Git ranges #1926
Comments
So I've got a better understanding of what's necessary for future reference: Some of these Curl records have both a SEMVER range and a GIT range, and some don't:
If I'm understanding correctly, the ones without a GIT range are a) missing from whatever list was screenshotted (@jess-lowe how did you get that list?) Getting the vulnerability page just right for a number of edge cases has proven to be a bit of a gnarly problem... |
This issue has not had any activity for 60 days and will be automatically closed in two weeks |
This issue has not had any activity for 60 days and will be automatically closed in two weeks See https://github.com/google/osv.dev/blob/master/CONTRIBUTING.md for how to contribute a PR if you're interested in helping out. |
Some of the older curl vulnerabilities have nothing to distinguish their 'package' or ecosystem so aren't being categorized and therefore shown on osv.dev. Despite CVE-2016-8616 existing in datastore, it is not visible on the website.
Possible fixes could include some sort of "reverse git enumeration" where we look up commits from tags (instead of the tags from commits we currently do)
The text was updated successfully, but these errors were encountered: