Talk:Common Vulnerabilities and Exposures

Latest comment: 3 years ago by Zeikonaut in topic Different Acronym

Modified

edit

Perhaps this article should be modified, as the CAN- prefix has not been used for new vulnerabilities since 2005/10/19 [1]. 192.216.212.193 (Talk) 12:12, 5 October 2007 UTC

Maintenance of page

edit

I'm actually the guy that does the CVE assignments for Red Hat and by extension a lot of Open Source projects so as things change I'll make en effort to keep this page in sync. If you have any questions please email me at kseifried@redhat.com Seifried~enwiki (talk | contribs) 03:08, 6 July 2013 (UTC)Reply

Singular and plural

edit

I think the article should be renamed to Common Vulnerability and Exposure (the singular) since people in general do write CVEs as the plural. 79.168.46.147 (talk) 23:26, 17 December 2015 (UTC)Reply

Missing paragraph about what is CVE worthy

edit

The whole article does not go into any detail about what kind of vulnerabilities are CVE worthy. It is noteworthy, that not each and every software problem is CVE worthy. There are some generic guidelines about vulnerabilities and exposures [1], but all of this is not an exact science, and there is (ongoing) discussions on how to handle some specific cases [2]. — Preceding unsigned comment added by Karol Babioch (talkcontribs) 21:44, 4 March 2018 (UTC)Reply

References

Different Acronym

edit

Greetings,

reading through the original paper that MITRE has on their CVE website (https://cve.mitre.org/docs/docs-2000/cerias.html) i think it should be at least noted somewhere in the article, that back then in 1999 CVE was acronym for Common Vulnerability Enumeration. Because i first thought, that Common Vulnerabilities and Exposures is a mistake, but it's right since it's listed under acronyms here at the end of the page: https://cve.mitre.org/cve/cna/rules.html Zeikonaut (talk) 22:34, 25 July 2021 (UTC)Reply