-
Notifications
You must be signed in to change notification settings - Fork 30
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
add exploit \ epss for cves #632
Comments
👋 Hey @TimBrown1611 thanks so much for the issue - Here is a quck summary of what we can currently do: Here we took a bucket of SBOM from the top 100 images on docker hub and sliced them against only showing vulnerabilities that were in the 0.995th percentile marker for EPSS data downloaded on 2024-06-03. We're also looking at views that show trend lines over multiple days of epss data. Look for that in a blog post from Anchore coming soon. As to WHEN this will be available as data in the published grype-db and not something users need to match AFTER the fact I defer to @wagoodman who is working on the schema v6 for grype currently. Thanks for the enhancement request! |
We're planning on adding KEV and EPSS data to grype in the near future -- this will be unlocked by the grype DB v6 work in the near future (anchore/grype#2128). |
This is related to the ask in Grype: anchore/grype#1973 |
hi! |
What would you like to be added:
for each CVE provide also the epss score based on this - https://www.first.org/epss/
Why is this needed:
calculate better the risk for each CVE
Additional context:
The text was updated successfully, but these errors were encountered: