Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by fauchletenerum on Friday November 20, 2026 @12:55AM
(#50570684)
I'm not sure how cost effective or even viable that option would be. I think the only practical defense is some kind of baseline hardening at the OS or application level. Something like eBPF rules i.e. what Cilium Tetragon policies provide. Basically it seems like there's no way to guarantee that your application code can't be exploited in some novel way so your best option is to restrict them as much as possible.
[ Parent
| on HN ]
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by shepherdjerred on Friday November 20, 2026 @02:28AM
(#50571314)
I'm really just talking as a layman here.
My feeling is that if we use traditional security approaches that seems like a losing strategy. You cannot just keep patching. I mean obviously you should, but that is not enough.
LLMs are finding zero days in operating systems, language runtimes, everything. They will definitely be finding holes in your API. It is not a question of 'if'.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by fauchletenerum on Friday November 20, 2026 @03:06AM
(#50571581)
I agree that patching is just plugging holes in the dam with your fingers. I think the only viable defense is something more low level in the kernel. SELinux, eBPF, or something new and more sophisticated than those. A lightweight agent passively monitoring system calls and detecting anomalies perhaps?
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by LtWorf on Friday November 20, 2026 @08:12AM
(#50574207)
And what would that solve?
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1...
by fc417fc802 on Friday November 20, 2026 @03:20AM
(#50571705)
> there's no way to guarantee that your application code can't be exploited in some novel way
As a thought experiment if this hypothetical application code were written in something resembling haskell I suspect it would actually prove fairly difficult if not impossible to find novel ways to exploit it. I think at that point an attackers only options are logical inconsistencies in the underlying business logic (see that one NASA rocket) or bugs in the compiler and runtime.