you are viewing a single comment's thread
view the rest of the comments
[–] 12 points 10 hours ago (1 child)

You're right, at the least the name should have the year in it so that we know if it's a new vulnerability or an old one.

And since a product can have multiple vulnerabilities in the same year we should have a number that increments with each new vulnerability found.

Also, since one vulnerability can affect multiple products (eg. a vulnerability in a library), we can't use the product names to identify the vulnerability (as that could be quite a long list). We will just use the acronym for our naming scheme so that we can distinguish our list of numbers from other lists of numbers like book ISBNs or ICQ numbers.

We could call our naming scheme the Cool Vulnerability Eponym.

So the vulnerability name would end up as something like CVE-2026-123456.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 7 points 10 hours ago

    Lol, nice backronym! CVEs are great! They’re not very scannable in headlines, though. For that I would actually prefer product name to be involved. Just maybe not written as a Fast and Furious movie title.

  • source
  • parent