Fix VulnDB parser being unable to import vulnerability records when 'nvd_additional_information' is empty #3437
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Without this condition, parsing 'nvd_additional_information' as an empty array would fail. This fixes DependencyTrack#3436. Signed-off-by: Lukas Braune <[email protected]>
nscuro
added
defect
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Without this condition, parsing the
nvd_additional_informationfield given as an empty array would fail. This fixes #3436.Description
A condition was added to DT's VulnDB parser that checks whether the
nvd_additional_informationfield of a vulnerability record is empty and skips its processing. Otherwise, the parsing would fail as described in #3436.Addressed Issue
Additional Details
Checklist