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

The NVD plans to retire the remaining legacy data feeds as well as all 1.0 APIs. #725

Closed
m-1-k-3 opened this issue Jul 29, 2023 · 11 comments · Fixed by #913
Closed

The NVD plans to retire the remaining legacy data feeds as well as all 1.0 APIs. #725

m-1-k-3 opened this issue Jul 29, 2023 · 11 comments · Fixed by #913
Assignees
Labels
cve-search Some cve-search question/issue EMBA in progress Someone is working on this issue in 3rd party component something in a 3rd party component we are using prio Sponsored priority issue question Further information is requested Research

Comments

@m-1-k-3
Copy link
Member

m-1-k-3 commented Jul 29, 2023

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

image

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?

@m-1-k-3 m-1-k-3 added question Further information is requested cve-search Some cve-search question/issue issue in 3rd party component something in a 3rd party component we are using prio Sponsored priority issue labels Jul 29, 2023
@github-actions
Copy link

This issue is stale because it has been open for 28 days with no activity.

@github-actions github-actions bot added the stale label Aug 27, 2023
@BenediktMKuehne BenediktMKuehne added in progress Someone is working on this and removed stale labels Aug 28, 2023
@m-1-k-3
Copy link
Member Author

m-1-k-3 commented Sep 2, 2023

image

a bit more time ...

@m-1-k-3 m-1-k-3 added the EMBA label Sep 14, 2023
@m-1-k-3
Copy link
Member Author

m-1-k-3 commented Sep 14, 2023

@m-1-k-3
Copy link
Member Author

m-1-k-3 commented Oct 11, 2023

Looks as CVE-search is getting a new importer cve-search/cve-search#1010 (comment)

@P-T-I
Copy link

P-T-I commented Oct 11, 2023

@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!

Copy link

github-actions bot commented Nov 9, 2023

This issue is stale because it has been open for 28 days with no activity.

@m-1-k-3
Copy link
Member Author

m-1-k-3 commented Nov 17, 2023

Working on this. See #884 and #887
Further testing needed

@m-1-k-3
Copy link
Member Author

m-1-k-3 commented Nov 18, 2023

see also #892

@m-1-k-3
Copy link
Member Author

m-1-k-3 commented Nov 21, 2023

should be done by #899

@m-1-k-3 m-1-k-3 closed this as completed Nov 21, 2023
@m-1-k-3
Copy link
Member Author

m-1-k-3 commented Nov 21, 2023

It is now recommend to setup a NIST API key
See also https://github.com/e-m-b-a/emba/wiki/Installation#prerequisites

@m-1-k-3 m-1-k-3 unpinned this issue Nov 23, 2023
@m-1-k-3 m-1-k-3 reopened this Nov 24, 2023
@m-1-k-3
Copy link
Member Author

m-1-k-3 commented Nov 24, 2023

Reopen it until final solution is finished. Currently working on a full replacement

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cve-search Some cve-search question/issue EMBA in progress Someone is working on this issue in 3rd party component something in a 3rd party component we are using prio Sponsored priority issue question Further information is requested Research
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants