Non-CVE vulnerabilities
Non-CVE vulnerabilities
Posted Jul 25, 2025 11:15 UTC (Fri) by smcv (subscriber, #53363)In reply to: Non-CVE vulnerabilities by pabs
Parent article: Understanding Debian's security processes
For vulnerabilities with no CVE ID, Debian's security tracker does have a concept of allocating temporary IDs like "TEMP-2025-012345" if necessary. For best results, upstreams should apply some sort of unique ID to vulnerabilities (an upstream bug-tracker number, or their own local IDs similar to Github GHSA) so that they can set the scope for what they consider to be in-scope for a particular vulnerability and what they consider to be a separate issue; if they do that, it's easy for Debian to say that TEMP-2025-012345 is just another name for fooproject/foo#123 or whatever.
Posted Jul 25, 2025 13:13 UTC (Fri)
by pabs (subscriber, #43278)
[Link]
ISTR that other projects have their own vulnerability ID space, and not all of them have corresponding CVEs too.
I also note Debian doesn't seem to either auto-import non-CVE vulnerability data (probably too many to ingest, and most aren't for Debian-packaged projects anyway), nor map non-CVE vulnerability IDs to CVE or TEMP IDs.
I expect the combination of these means that Debian does probably miss some vulnerabilities where upstreams didn't get CVEs, but have released vulnerability information with a GHSA or other ID system.
Non-CVE vulnerabilities