a CVE dispute

A few years years ago the curl project signed up and became a CNA. This means that we are masters of and can allocate our own CVE identifiers. For any security problems within our territory, it is we who decides if the issue should get a CVE our not. No more bogus CVEs. 57 CVEs … Continue reading a CVE dispute →

daniel.haxx.se

@bagder would nominating https://www.cve.org/PartnerInformation/ListofPartners/partner/redhat as your CNA's root help avoid MITRE?

MITRE sits above other roots, but if the processes flows to Pete's group first it might squelch the noise https://www.cve.org/programorganization/Structure

@eslerm our root is Red Hat already. I don't know why MITRE was involved here

@bagder @eslerm Perhaps they pitched a fit to Red Hat & appealed it up to MITRE. I’m not familiar with the process, but this seems like the type of person to use it. They had an AI find the bug and write the report, then went back to it to seek validation. Meanwhile, their AI entirely missed the invalid DNS issue. Meanwhile, I brought the same URL to ChatGPT and it pointed out the invalidity immediately.

AI is rotting brains.