https://nvd.nist.gov/vuln/detail/CVE-2021-3682 has this CPE: cpe:2.3:a:qemu:qemu:6.1.0:-:*:*:*:*:*:* That means "not 6.1.0". This isn't handled by our comparison logic as this CVE gets reported although have 6.1.0. References to the specs: https://nvlpubs.nist.gov/nistpubs/Legacy/IR/nistir7695.pdf https://nvlpubs.nist.gov/nistpubs/Legacy/IR/nistir7696.pdf
The hyphen ("-") in the given CPE is part of the update field. This field allows specifying the update name of the version. From my understanding of the linked documentation, CPE should be read as follows: cpe:2.3:a:qemu:qemu:6.1.0:rc1:*:*:*:*:*:* points to 6.1.0-rc1 cpe:2.3:a:qemu:qemu:6.1.0:-:*:*:*:*:*:* points to 6.1.0, with no update applied cpe:2.3:a:qemu:qemu:6.1.0:*:*:*:*:*:*:* points to all updates of 6.1.0 If I misunderstood the notation, can you please point to the part of the doc detailing the usage of hyphen to means "not in"? If I did understand the notation correctly, then I think the issue is in NVD, and the line cpe:2.3:a:qemu:qemu:6.1.0:-:*:*:*:*:*:* should not be listed as impacted configuration. And in that case I think cve-check works as intended
Ross, what do you think about the above comment? (Setting NEEDINFO and owner)
I like that argument. Geoffrey: would you be willing to contact NIST and get the CPE updated? If they accept the changes, I was wrong, and we can close this bug
Ross, I have sent a mail to NVD for change. I will update the ticket as soon as I have news
I already have news, NVD approved the change and the CVE page is already updated: https://nvd.nist.gov/vuln/detail/CVE-2021-3682 Therefore, I am closing this ticket.
Perfect, thanks!