Comment 1 for bug 1750473

Revision history for this message
Colin Watson (cjwatson) wrote :

That just means that our system hadn't scanned that CVE number from Mitre's database yet - we scan it daily. We seem to have picked up that CVE now, judging from our logs:

2018-02-20 08:47:42 INFO CVE-2017-18191 created
2018-02-20 08:47:42 INFO Creating new CONFIRM reference for 2017-18191
2018-02-20 08:47:42 INFO Creating new CONFIRM reference for 2017-18191

... so could you please try again?