You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
I have been looking at the nvd 2.0 API, and I noticed that they have CWEs of the form NVD-CWE-{noinf\other} in addition to CWE-{num},
My implementation prioritizes CWEs of the normal kind, and if there are CWEs with number and NVD-CWE-{noinf\other}, the one with number will be selected.
I also noticed that multiple CWE sources have the same number, and they may be duplicated. I have also solved this problem.
In cases where only NVD-CWE-{noinf\other} has a vulnerability, we leave it alone.
I kept the further logic as it was.
Below I will give examples with the API and how it is now stored in mongo
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.
Add a CWE array to the support #309