This is what the #CVE and CPE system does.
We can chose to make the system different.
https://github.com/madler/zlib/issues/868#issuecomment-2807804350
This is what the #CVE and CPE system does.
We can chose to make the system different.
https://github.com/madler/zlib/issues/868#issuecomment-2807804350
I’m actually quite OK with this.
The broader community is very good at detecting situations like these as damage, and routing around.
Just like the Internet. Right?
We had public disclosure and known vulnerability databases before CVE. And nothing is stopping those who have a shared need from coming together to fill a vacuum…
#cve
Reflecting tonight on the #CVE program, all it has given us, and how frustrated I’ve been because of what does, and what it fails to do.
Unfortunately there is no point in claiming that the purpose of a system is to do what it constantly fails to do…
I frequently grump about what the #CVE system has become in practice. Folks may think that I’m not a proponent of the program. That’s not true at all. I’m an advocate for it, and for all those who pour their time and talent into it (often voluntarily).
But, IMO it is an overstatement to say that a CVE is a critical element in coordinating response to emerging vulnerabilities like heartbleed or log4shell. Embargoed critical vulns are rarely identified with CVEs among defenders.
@GossiTheDog but do they need to be?
How many of them need to be actively managed in a globally coordinated way?
Should every organization attempt to interpret the information present in CVEs, and the CVE information ecosystem _directly_?
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.