-
Notifications
You must be signed in to change notification settings - Fork 11
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: Support for NIST NVD CVE Change History API #920
Conversation
Conventional Commits Report
🚀 Conventional commits found. |
Codecov Report
@@ Coverage Diff @@
## main #920 +/- ##
==========================================
+ Coverage 90.32% 90.43% +0.11%
==========================================
Files 95 97 +2
Lines 6666 6745 +79
Branches 957 968 +11
==========================================
+ Hits 6021 6100 +79
Misses 441 441
Partials 204 204
📣 Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today! |
7a8aabb
to
e803227
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks very good already. Could you do me an additional favor and implement the changes from #919 where i've added requesting a specific number of results? Should be straight forward.
Co-authored-by: Björn Ricks <bjoern.ricks@greenbone.net>
Co-authored-by: Björn Ricks <bjoern.ricks@greenbone.net>
What
This PR adds support for NIST NVD CVE Change History API (see https://nvd.nist.gov/developers/vulnerabilities#divGetCveHistory).
Why
To query for changes of CVEs.
Notes:
https://csrc.nist.gov/schema/nvd/api/2.0/cve_history_api_json_2.0.schema specifies the
eventName
to be astring
and not an Enum with predefined values. https://nvd.nist.gov/developers/vulnerabilities#cveHistory-eventName however specifies specific values, so I used an Enum anyways.References
VTA-463
Checklist