-
-
Notifications
You must be signed in to change notification settings - Fork 218
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
The NVD plans to retire the remaining legacy data feeds as well as all 1.0 APIs. #725
Comments
This issue is stale because it has been open for 28 days with no activity. |
Looks as CVE-search is getting a new importer cve-search/cve-search#1010 (comment) |
@m-1-k-3 The importer is provided by the cve-search/CveXplore package; feel free to check it out and post me the comments! |
This issue is stale because it has been open for 28 days with no activity. |
see also #892 |
should be done by #899 |
It is now recommend to setup a NIST API key |
Reopen it until final solution is finished. Currently working on a full replacement |
CVE-Search is our main tool for the CVE lookup functionality in the F20 module. These results are then the base for further lookups to Metasploit, Exploit-DB and other PoC databases.
As NIST will retire the legacy data feeds in September we need to evaluate the consequences for EMBA:
https://nvd.nist.gov/General/News/change-timeline
Currently I'm not sure how hard this will hit cve-search and as a consequence also EMBA. It looks as cve-search are working on this here.
Currently I do not know if we have the possibility to further use and update cve-search after September.
Someone out there with more insights on this topic? Probably someone already tested vulnerability-lookup and can share his experience and some results?
The text was updated successfully, but these errors were encountered: