2018 CVEs not getting processed.

Question

i have updated the urls for the vulnerability data import with the link to the 2018 xml file, I can verify that the file is downloaded nightly and in the directory with the rest of the files. However I do not see any CVEs from 2018 file getting applied to my devices.

There is one specifically that I know should be applied to the cisco ASAs, CVE-2018-0101.

Any input or suggestions will be greatly appreciated.

jtimes · Answer

With this in mind:  NVD - XML Vulnerability Feed Retirement 
I'm certain SolarWinds is working on the transition to JSON feeds, although I haven't personally confirmed it

foonly · Answer

I know this is an old post, but I'm also seeing problems with 2018 data.

We have 3 separate installs of NCM, and no two have the same NCM_VulnerabilitiesAnnouncements tables for any year, except 2001-2007, 2009 and 2010.

The only XMLs we are downloading nightly are:

http://static.nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-recent.xml.zip

http://static.nvd.nist.gov/feeds/xml/cve/nvdcve-2.0-modified.xml.zip

I don't think we ever edited that, and those appear to be the defaults listed in the NCM Administrators Guide.

Those XMLs don't list every CVE, even for 2019. We have CVE's for 2019 in the database that are not in the latestnvdcve-2.0-recent.xml and vice versa.

So I wonder if NCM only keeps CVEs for models or MachineTypes that exist in the DB at the time of XML download.