Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
This PR fixes a now incorrect event name. It not only changes this string expected from the NVD, but also the Enum value on our side.
Why
As announced in https://www.nist.gov/itl/nvd / https://groups.google.com/a/list.nist.gov/g/nvd-news/c/pTfvMzIWGxg, the
CVE Received
event has been renamed toNew CVE Received
.Without this change the parsing fails:
With this change this is now fixed:
I also decided to adjust the Enum value accordingly. It is very likely not an issue, because IIRC only vt-cve-library is using the CVE Change History and no one is using the
CVE_RECEIVED
value anyways (see here).References
Checklist