Version 4.0.2 can not download NVD
See original GitHub issueDescribe the bug I constantly see the next messages:
An exception occurred downloading NVD CVE - 2008
Some CVEs may not be reported.
** Version of dependency-check used ** The problem occurs using version 4.0.2 of the gradle plugin.
** Log file ** https://gist.github.com/emartynov/73291c24c2fb8e09e8c2f9aa69941ac2
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Unable to download the NVD CVE data - Stack Overflow
when i do build am getting Unable to download the NVD CVE data.do I have to include any dependency to resole that issue...
Read more >CVE-2021-44228 - NVD
Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.
Read more >CVE-2021-24825 - NVD
Current Description. The Custom Content Shortcode WordPress plugin before 4.0.2 does not validate the data passed to its load shortcode, ...
Read more >Data Feeds - NVD
If no changes have been made there is no benefit to downloading either the .zip or .gz files. This approach should result in...
Read more >CVE-2021-22819 Detail - NVD
CVSS Version 2.0 ... NIST does not necessarily endorse the views expressed, ... https://download.schneider-electric.com/files?
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The entire downloading of the NVD has been re-written for the soon to be published 5.0.0. The NVD has changed their rate limiting. You can try the 5.0.0-M3 milestone release to see the changes - or wait hopefully less then a week for the 5.0.0 release.
@emartynov if the 60 modules are all in a single build - there should be no issue as the update process use a lock and waits to make sure only one instance of ODC is updating the database at a time.