-
Notifications
You must be signed in to change notification settings - Fork 594
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
CVE published date field available in the report #1355
Comments
This looks like a great addition and we'll look to add this to Grype! It looks like we're reading this information from NVD but we would need to update the Grype DB to get it included; we'll add this to the backlog. Thanks for bringing this to our attention! |
Hey @westonsteimel do you have any other thoughts on this? |
It will be a huge enhancement. Looking forward to this feature. |
+1 |
+1 - this would make it possible to apply CVE fix SLAs. |
+1 |
+1, this is a must-have. Specially to prioritize issues by age. |
Getting to include CVE Published Date from NVD would help a lot in order to automate results report content. |
+1, this would help to work properly with SLAs regarding a given CVE. |
What would you like to be added:
We would like to request an additional filed(s) to be added to the report produced by
grype
that would enable us to tell when a CVE has been published and last updated.Why is this needed:
Currently this information doesn't seem to be available in the JSON output.
Additional context:
This is for the purpose of reporting.
The text was updated successfully, but these errors were encountered: