logoalt Hacker News

userbinator • today at 3:50 AM • 5 replies • view on HN

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.


Replies

jtrn • today at 11:27 AM

THIS!!!!!!!!!!!!!!! THIS times 10000!

I'm starting to get annoyed about the OMG OMG BREAKING BREAKING ALARM-EMOJI crap that's not a real emergency.

Four times in the last month, I dropped everything and started investigating whether a serious CVE related to any of our dependencies warranted an emergency bump, only to be frustrated that images, even from AWS, did not have the fix yet. So then I had to worry about whether I should build from source. We actually built PHP from source and deployed it to prod, just to get ahead of the PHP2Shell vulnerability

But yesterday's PHP vulnerability, CVE-2026-115560, didn't even apply to us or most people running PHP, and I don't think there are any realistic working exploits out there. I'm not saying that it's not possible, but I'm starting to feel that there's a large difference between what's theoretically possible and what's practically possible. And given the storm of patches and vulnerabilities found, this will become increasingly important to ask.

I think everything above a CVE score of 9.0 should warrant some level of “how exploitable is this in real life,” and anything above 9.5 should be proven to be easy for an attacker to execute, not just “possible in theory.” I don't see how we will survive as developers if there isn't some sort of better triage for vulnerability severity assessment. If everything is an emergency, then nothing is an emergency.

➕ show 3 replies
jeroenhd • today at 1:16 PM

CVSS scores do not indicate priority. They give a baseline so you can pick what CVEs affecting you you should do risk analysis for first.

The score is just fine. The people misinterpreting everything with a CVSS score higher than 8 as the end of the world are panicking over nothing.

➕ show 2 replies
zzril • today at 10:18 AM

"Internal"? It's documented in the `libssl-dev` manpages.

(Although I agree it should be an internal function.)

tptacek • today at 3:52 AM

(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.

➕ show 4 replies
nizbit • today at 9:47 AM

Time is a construct. CVSS is a vibe.