3 ms·
I’d usually agree, but 9.6 indicates this is something you probably want to patch sooner rather than later.
by kstrauser 6y ago
I’d usually agree, but 9.6 indicates this is something you probably want to patch sooner rather than later.
- tptacek 6y agoNo, it doesn't. That's exactly the problem. You can make CVSS say whatever you want it to. You can see the problem on this very thread. Josh Triplett points out that (unlike the screen variant of the vulnerability), the xterm vulnerability requires user interaction: you have to select the text. And yet it has practically the maximum possible CVSS score. What does CVSS even mean if the difference between a zero-interaction drive-by RCE and one that requires an idiosyncratic user interaction is just 0.4 points?
- kstrauser 6y agoI completely agree with that. I think it’s still a useful shorthand for “hey, you might want to take a look at this one”.
- tptacek 6y agoOnce again: my point is that it is the opposite, because you can make lots of vulnerabilities read out this way even if they're not at all urgent --- and the opposite thing is true, very severe vulnerabilities can also get surprisingly low scores. CVSS is literally a Ouija board. I'm not just calling it that because it's unreliable or based on superstition. I'm saying that the process of arriving at a CVSS score is Ouija-like: you fill out a calculator or something, get a score that has no relation to your intuition of the severity of the vulnerability, and start applying small bits of pressure here and there to land on the score you know the vulnerability should land on. In fact: if you don't do that, you get exceptionally dumb CVSS scores for everything. It's a mess. If you want to call out the severity of a vulnerability, you should do so with objective facts. "Remote code execution" is a good tip-off. "CVSS 9.6" is not.
- kstrauser 6y agoI understand what you’re saying and generally agree. We get incoming bug bounty reports like “drop everything, here’s a 9.8 you need to fix right now!” that turns out be a misunderstanding. But in the case where multiple vendors have scores like: - Amazon: Important (https://alas.aws.amazon.com/AL2/ALAS-2021-1619.html https://alas.aws.amazon.com/AL2/ALAS-2021-1619.html) - Ubuntu: 9.8 (https://ubuntu.com/security/CVE-2021-27135 https://ubuntu.com/security/CVE-2021-27135) - Red Hat: 9.6 (https://access.redhat.com/security/cve/CVE-2021-27135 https://access.redhat.com/security/cve/CVE-2021-27135) …it starts to look like there’s consensus that not only is there an RCE, but it’s really easy to exploit. I think that’s where CVSS starts to come in handy. An RCE is bad, but one that’s trivial to actually use is extra bad. And yes, CVSS absolutely has some Ouija properties, but it’s the most commonly used metric I’ve seen for communicating how bad a vulnerability actually is. In this case, it wasn’t just the reporter who said it was bad but all the affected vendors agreeing with them.
- tptacek 6y agoUbuntu is just taking the score from NVD. Redhat has applied the first Ouija input to it, adjusting it to "user interaction required". That changed the score from a 9.8 --- 0.2 points from the maximum possible CVSS score --- all the way down to... 9.6. I can't think of a better illustration of how bad CVSS is. Once again: my point isn't that the vulnerability is unimportant (though: it's not nearly as important as it likely seems) or that it doesn't belong on the HN front page (it is a very, very funny vulnerability). It's simply that we should not be editorializing CVSS scores into titles, or taking CVSS scores seriously when they occur organically in titles. CVSS is very, very bad. It is the CISSP of security metrics.
- Arnavion 6y agoIn what universe is selecting text in a terminal an "idiosyncratic user interaction" ?
- tptacek 6y agoYou have to select exactly the right text, and that text will never look like "select this right now" --- if you've seen the characters we're talking about, it's like Zalgo text. Selection in an xterm is not the ordinary response to these strings. This is a little like Clickjacking, where you'd expect a bounty hunter to come at you with "this very severe bug can be triggered simply by clicking", and you respond "well, we should fix that, but users never click in those places, so we're going to send you a t-shirt" and the bounty hunter responds "no, clicking is a fundamental user interaction, you should send me $5000". And my point isn't even that this is a dumb bug (certainly, it's not as dumb as CJ usually is). It's that there is absolutely no fucking way it is a 9.6 on a 10.0 scale of severity. Shellshock, ffs, has the same NVD CVSS as this bug. Shellshock doesn't even care what terminal you're using.
- Arnavion 6y ago>if you've seen the characters we're talking about, it's like Zalgo text. Selection in an xterm is not the ordinary response to these strings. Yeah, with all due respect, you're not in touch with what ordinary responses are. When people see zalgo like the infamous SO regex post, selecting it is the first thing they do.