Remix.run Logo
▲ userbinator 4 hours ago

I think CVSS 9.8 is exaggerated. This is not remotely anywhere near as serious as Heartbleed. It's an internal function which will fail if its input is far too long, but exploitability rests on how untrusted input can reach it; the key word being "untrusted". E.g. if you operate a base64 encoding service on the Internet that just reads all the data into memory at once and calls EVP_EncodeBlock(), that's exploitable. If you have a protocol that involves a block of data with a 16-bit length field which is passed to EVP_EncodeBlock(), that's 100% safe.

For those wondering about TLS: speaking as someone who has written a TLS implementation, AFAIK neither base64 encoding nor decoding occurs in the protocol itself, and the longest length field is 24 bits (Hello stream). Certificate processing involves ASN.1 which does support arbitrarily-long integers, but that's a big hint to check that they're within a sensical range.

▲tptacek 4 hours ago | parent [-]

(I'm a broken record on this so I'll keep it brief). The problem here is that the CVSS score is in the headline, as if it meant anything. But CVSS doesn't mean anything. It's a Ouija board; VR people jack it up to get attention, vendors nerf it to chill their customers out.

Someone should design something better, and less malleable.

▲csnover 3 hours ago | parent | next [-]

A few years ago I participated in a study[0] about CVSS and apparently was very much in the minority in feeling that these scores are essentially useless. I have no idea what would actually shift the majority’s opinion on this, but I will at least echo your sentiment that everyone deserves something better.

[0] https://arxiv.org/abs/2308.15259

▲tptacek 3 hours ago | parent [-]

It's not an out-there opinion among vulnerability researchers, though.

▲vasco 32 minutes ago | parent | prev | next [-]

CVSS would be fine if they shared full vector rather than adding up the score. The vector is representative of what. Going from what to "how bad" through making it a single number is where they messed up because the weights usually don't make sense from case to case.

▲JJJollyjim 4 minutes ago | parent [-]

I don't see that being at all helpful in this case. Which part of the vector conveys "this is a library function, so everything from the attack vector to authentication requirements to impact depends on how your application is utilising it, if it is at all"? For a bug like this, anything you select for into those fields is a stab in the dark.

▲userbinator 3 hours ago | parent | prev | next [-]

I think tiny pieces of isolated code like this function simply cannot be assigned CVSS scores, because it's missing all the context and threat model around how it is used.

Then again, given that I once had to respond to a report which assigned a similar amount of severity to the strlen() function claiming that it will read beyond its bounds if its input is missing a null terminator (DUH!), I'm not surprised at the lack of critical thought among a certain population in this industry.

▲solyin 2 hours ago | parent | prev [-]

At the end of the day, sysadmins care about "how fucked am I" from an email subject line. A replacement system would be "let me run a daemon on your network telling me what you run" with vendors telling me about the vulnerabilies and I'll tell you if you (the sysadmin) give a shit. Technically that's trivial, but who's gonna trust me to run a daemon like that on their network. Maybe you'd have luck with your public history, but that seems like quite the uphill battle.