So, uh, like, any word on what the "9.8" actually means? Is this "an obscure feature nobody has on could with a bit of luck and a cosmic ray strike allow arbitrary code execution if you're one of the few people using it" or is this "if you have a socket with OpenSSL exposed to the internet you're already compromised" or what?
So this might be very similar to Java4shell, though will need to be verified.
This is another base64 encoder where it takes a blob and coverts it to base64. I'm assuming an attacker control bit of data could be passed to the function which then overflows. Not sure if it can attempt to control a valid address or not, but unlocked AI likely could pretty quick.
Since no enterprise distro has shipped OpenSSL 4 yet, it will only be an issue if you are running an upstream distro on a personal machine.
This was possibly a rhetorical question but apparently it goes something like this - just a simple formula someone came up with that tries to model badness:
(using Github's values from https://github.com/advisories/GHSA-83xj-7xh4-4p7x)Interesting that the impact calculation treats C, I, A as equal. And of course a lot of those inputs are just human(?) supplied vibes and/or context dependent in your use case.