You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As cve-search aggregates various sources of vulnerability, it's not uncommon to get vulnerability without CVE assignment. The idea is to allocate an UUID at the import to ensure a unique identified within
a cve-search installation or beyond cve-search.
The proposal, in a near future, would be to support a public version of cve-search were security researchers could get an UUID for a vulnerability without the need to ask a CVE NA. This UUID could be
used as an unique reference later on even if there is no official CVE assignment or vendor assignment.
The text was updated successfully, but these errors were encountered:
As cve-search aggregates various sources of vulnerability, it's not uncommon to get vulnerability without CVE assignment. The idea is to allocate an UUID at the import to ensure a unique identified within
a cve-search installation or beyond cve-search.
The proposal, in a near future, would be to support a public version of cve-search were security researchers could get an UUID for a vulnerability without the need to ask a CVE NA. This UUID could be
used as an unique reference later on even if there is no official CVE assignment or vendor assignment.
The text was updated successfully, but these errors were encountered: