Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by jerf on Thursday November 19, 2026 @09:50PM
(#50569564)
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?
[ Parent
| on HN ]
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by pixl97 on Thursday November 19, 2026 @10:08PM
(#50569680)
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.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by fulafel on Friday November 20, 2026 @01:15AM
(#50570812)
This was possibly a rhetorical question but apparently it goes something like this:
# 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.914816
impact = 6.42 \* impact_sub_score # -> 5.87311872
exploitability = (
8.22 \* attack_vector \* attack_complexity \* privileges_required \* user_interaction) # -> 3.887042775
score = impact + exploitability # -> 9.760161495
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by arch-choot on Friday November 20, 2026 @02:19AM
(#50571247)
CIA psyop confirmed? (/s)