A new release is now available for the cvechecker application. This is a stupid yet important bugfix release: the 3.7 release saw all newly released CVEs as being already known, so it did not take them up to the database. As a result, systems would never check for the new CVEs.

It is recommended to remove any historical files from /var/lib/cvechecker/cache like so:

~# rm /var/lib/cvechecker/cache/nvdcve-2.0-2017.*
~# rm /var/lib/cvechecker/cache/nvdcve-2.0-modified.*

This will make sure that the next run of pullcves pull will re-download those files, and attempt to load the resulting CVEs back in the database.

Sorry for this issue :-(


Comments

To comment as a guest, use "Or sign up with disqus" and then select the "I'd rather post as guest" option.

comments powered by Disqus