5 ms·
So, uh, what's the problem? CVEs are just meant to ensure that we're all talking about the same bug when we're talking about a bug. If you're making a big deal
by tptacek 3y ago
So, uh, what's the problem? CVEs are just meant to ensure that we're all talking about the same bug when we're talking about a bug. If you're making a big deal about a CVE existing for a bug you don't care about... that's on you?
- hannob 3y agoThis is the problem: "Service-level contracts and governmental requirements mean that a critical CVE needs to be addressed in short order, so non-critical bugs that get marked that way can cause real problems." You are right what CVEs are, but there are plenty of people who think CVEs are something different.
- thephyber 3y agoThe CVEs aren’t the problem. You are describing the problems related to Vogons who assume all bureaucratic inputs are perfect. All tickets should have an escape hatch where some person with direct experience with the software can report false positives or “not an issue”. Those are different than the purpose of the article, which is describing the variance of quality of CVE data.
- waihtis 3y agoNot to mention the completely trash cyber risk ratings industry. If you score poorly in because of their absurd scoring methods, it will potentially impact revenue streams if you have to deal with vendor risk departments, etc who don't understand any of the underlying mechanics
- mxmlnkn 3y agoSeems like someone has to file a CVE regarding CVE scores leading to DOS attacks on the developers.
- tptacek 3y agoThe worst possible response to that problem would be to run the CVE program in a way that ratifies it going forward!
- 112233 3y agoBecause of incoming CRA and existing requirements, having CVE causes wide, lasting, high impact consequences for people maintaining software and hardware products, infrastructure and services. Since barrier of entry for CVE is as low as "logged in user can crash system by filling disk/ram, can cause data leak i think" and that thing can get assigned high marks depending on the randomness of this whole process, you are in a situation of "one bogus report to cripple all users of open source library" cve is not a bugzilla
- thephyber 3y agoWho is more likely to be able to score a CVE accurately — a nameless faceless CVE triager at NIST (or similar organization) who is working as a liaison between the reporter and the maintainer… or the maintainer himself? The CVE is a pure record. It has not guarantee of accuracy and should be treated with this knowledge. That’s what tptacek’s comment is saying. People who attach all sorts of contractual requirements on the assumption that every CVE is perfectly reported and recorded are setting themselves up for inevitable garbage-in, garbage-out situations. Also, if you’re curious, you should check out his post history. He’s kinda famous on HN in the security space.
- 112233 3y agoYes, please, tell all those auditors, security scanner vendors and journalists that they should treat CVEs with this knowledge. That having report with "1 critical vulnerability (CVE-2082-555) !!!!" does not mean that you have a security problem, and your equipment vendor has to drop everything and go fix that. You are telling me what CVE is. I am telling you what the effect of having CVE is.
- msm_ 3y agoI mean, do tell them that because you're right. CVEs are not broken, your auditors, security scanner vendors and journalists are. Sounds like if you replace CVEs with another system you'll get exactly the same mess.
- batch12 3y agoI agree, there's a lot of confusion between a CVE and CVSS. One is just an identifier, the other is its score. I am much more of a fan of using CVEs than assigning arbitrary marketing terms like xBleed.
- akerl_ 3y agoCVSS scores might as well be random dice rolls. They’re outright useless.
- rainonmoon 3y agoFunnily enough the current webp situation is the perfect counterpoint and sort of speaks to the fairly unregulated way CVEs are assigned. Multiple CVEs for the same core issue playing havoc and hampering remediation. A more robust system would indeed promise that we're all talking about "the same bug"; we aren't, currently. Then there's the erroneous CVEs closer to what OP is talking about, like more recent CVEs registered for deliberately vulnerable apps like OWASP Juice Shop etc. In practice, the current system gets a lot right, but its lack of scrutiny creates issues.
- cpach 3y agoI guess the problem is that people use automated scanning tools, see CVE:s with high scores and then they go and put pressure on FOSS maintainers about stuff that’s a) not urgent b) doesn’t have a high impact?
- yankput 3y agoIf there is a bug severity reported, the severity should be right; otherwise the score system should be entirely removed. If the CVE database was just codes and descriptions that would be ok. That’s not what people are complaining here about though
- akerl_ 3y agoI am in favor of the severity system being entirely removed. Attempting to score the vast majority of vulnerabilities against a universal axis is comical and falls apart as soon as you try any kind of real world application.