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

New importer: (old NVD JSON) to import as a standalone source #95

Open
adulau opened this issue Dec 9, 2024 · 2 comments
Open

New importer: (old NVD JSON) to import as a standalone source #95

adulau opened this issue Dec 9, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request new-feed

Comments

@adulau
Copy link
Member

adulau commented Dec 9, 2024

Following the issue reported here CVEProject/cvelistV5#6 (comment) - we need to continue importing the old NVD JSON in vulnerability-lookup.

Now the difficult question, should we use this FKIE source https://github.com/fkie-cad/nvd-json-data-feeds or the old (soon to be removed) source from NVD https://nvd.nist.gov/vuln/data-feeds ? I quickly checked and my preference is going for the FKIE one (as it's the same and already updated with some additional data).

The idea is to pivot from the CVE ID for this source (to have the additional metadata which was lost in the new CVE v5 part) and still consider the other NVD sources as the official ones.

@adulau adulau added the enhancement New feature or request label Dec 9, 2024
@Rafiot
Copy link
Collaborator

Rafiot commented Dec 9, 2024

The it repo is heavier, but also quite a bit simpler to initialize, so out of pure laziness, I'd go with that (it will also be quicker to add).

@adulau
Copy link
Member Author

adulau commented Dec 9, 2024

Perfect, let's go for the German updated NVD feed ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request new-feed
Projects
None yet
Development

No branches or pull requests

2 participants