-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
feat(fetch/nvd): use NVD API feed #348
Conversation
7839747
to
0289474
Compare
Thanks a lot. Tested OK with some basic tests. 👍 One question though: shouldn't there be some API key parameter somewhere on the CLI?
From API-Key-Announcement I have such a key ready to be used (a bit more difficult to actually test). I'll do my best to do further tests this week, but in the course of these tests and deployment I'll need to switch from v0.5.6 from 2020 I currently use to up to date v0.9.0, and probably re-initiate the MySQL DB is use for custom queries. |
(Note that of course, the API key support could as well be added later on, as another enhancement. As for me, I already have a lot to test here... Again, thanks for your work last weekend. 💯 ) |
Since we are not fetching directly from the NVD API, an API KEY is not required. This time, the results of the NVD API are saved in this repository(https://github.com/vulsio/vuls-data-raw-nvd-api-cve), and go-cve-dictionary uses that repository. |
I tested this successfully in a MySQL setup and my custom client application. 👍 I don't know Go, so this is a functional test only, not a code review, sorry for that. The next step for me will be to update my production server to v0.9.0, to be ready for the next version with this new development. Thanks again! |
Hi, is it related to https://nvd.nist.gov/vuln/data-feeds ? Best regards |
Although the version has not been clearly determined, go-cve-dictionary built after this PR was merged will use the results of the NVD API. |
Let me report v0.10.0 roughly.
|
@witchcraze |
Ah, OK.
|
As for the original data, depending on the source, you can tell whether it is evaluated by NVD or another vendor...... |
What did you implement:
Fixes #272
Type of change
How Has This Been Tested?
Checklist:
You don't have to satisfy all of the following.
make fmt
make test
Is this ready for review?: YES
Reference