-
Notifications
You must be signed in to change notification settings - Fork 235
Description
Matching CVEs and Software Bill of Materials is probably the hardest challenge when doing Vulnerability Management, because there is no way to agree on a unique ID of a specific product between vendor and user.
The current workflow is (on a very high level) as follows:
- Users create lists of components they use in their final product. This list contains the names of the components used in the final product along with the component's vendors.
- Users regularly scan the NVD / published CVEs for vulnerabilities matching vendor and name, to find CVEs for their components.
Agreeing on something like "product name" and "vendor name" is hard. Especially agreeing on a product name is hard, because there is a lot potential for ambiguity: Spaces, dashes, special characters (e.g. german Umlaute).
Many vendors are CNAs now.
Adding a field productId of type "uuidType" in the "product" object would be very beneficial. Vendors who are CNA can add - additionally to their product name - each time they publish a CVE for a specific product, the same product UUID to the CVE record. This would allow consumers of the CVE data allow to easily identify a product, independent of the product name.
I am sure this is not going to solve all problems with respect to matching CVEs and sBoMs. But I think the CVE JSON, along with the CNAs, is a pretty good place to have such an identifier.