upvote
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:

  # Hardcoded weights for AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  attack_vector = 0.85        # Network
  attack_complexity = 0.77    # Low
  privileges_required = 0.85  # None
  user_interaction = 0.85     # None
 
  confidentiality = 0.56      # High
  integrity = 0.56            # High
  availability = 0.56         # High

  impact_sub_score = 1 - (1 - confidentiality) \* (1 - integrity) \* (1 -  availability)  # -> 0.91 
  impact = 6.42 \* impact_sub_score                                                       # -> 5.87

  exploitability = (
    8.22 \* attack_vector \* attack_complexity \* privileges_required \* user_interaction)  # -> 3.88

  score = impact + exploitability                      # -> 9.76
(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.

reply
Not quite what I meant. Having been on the end of trying to establish CVE scores for bugs myself I am well aware that even two bugs of the "same score" can be very different in nature. A "push button, pop every website on the internet" is a 9.8-ish, but so is "nginx with this particular couple of config settings will yield a root shell for a particular request" even if it "only" affects 5% of the world, because "affecting 5% of every nginx install" is still fairly justifiably a high rating for all the scores. The scale tops out at the upper end.

Plus we're seeing "AI has found this bug and it looks super duper scary everyone panic" followed by two weeks later "well actually it took sustained and direct assault on a website and sometimes it didn't work and it was actually more like a 6.4" lately.

Geezus_42's "you probably haven't actually shipped this code anywhere anyhow" is more like what I was looking for.

reply
CIA psyop confirmed? (/s)
reply
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.

reply
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.
reply
This should probably be in the headline. I was trying to figure out why Debian didn't have an update.
reply
For real.
reply