News for hackers. Stuff that matters.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by shepherdjerred on Thursday November 19, 2026 @10:52PM (#50569928)
It feels to me the only way to beat LLMs finding vulnerabilities is to have LLMs (or LLMs paired with other AI methods) constantly monitor your infrastructure, traffic, database, etc. to ensure that nothing out of the ordinary is happening
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by tptacek on Thursday November 19, 2026 @10:53PM (#50569939)
I think so too; I think apart from pushing vulnerability research forward (which is important on its own merits just for computer science reasons), the major engineering challenge of this moment is figuring out how to make platforms resilient without rewriting everything; that could be better live-patching, it could be some weird monitoring thing, it could be automatic segregation and workload isolation.

It's not "just keep up with the patches". That's going to be a losing strat.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by NoDodgeQuestion on Friday November 20, 2026 @04:44AM (#50572364)
maybe today, you cant keep up, 2 year later, AI rewrite everything safe in rust, you wont need patch everday
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by Geezus_42 on Friday November 20, 2026 @05:06AM (#50572544)
Hahahahaha
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.
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.

Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by leptons on Friday November 20, 2026 @02:05AM (#50571131)
When Plex got hacked and my linux server had a cryptominer installed, I had no clue where to start fixing it. I loaded up Claude to analyze the system logs, and it told me what commands to run (and why) and the infection was gone in about 10 minutes. There's no way I would have known the many things I needed to do to fix and secure the system. I'm fairly new to Linux, and without the AI I would be helpless with some of the tricky things.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by kryptiskt on Friday November 20, 2026 @02:28AM (#50571311)
The right thing to do in that case is to save whatever data you need from the server and then nuke it thoroughly, which means all the disks should be wiped, don't keep the old UEFI partition around, and reinstall. It would preferable to skip the first step and get the data from a source that wasn't compromised, but sometimes you have bring out the hazmat suits to recover stuff from compromised systems.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by shepherdjerred on Friday November 20, 2026 @02:30AM (#50571329)
This is very reactive though -- imagine you were a business. You'd be screwed. Your data is already gone.
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by LtWorf on Friday November 20, 2026 @08:14AM (#50574219)
You're still helpless, since you didn't do what you should have done (format).
Re:OpenSSL: Buffer overflow in EVP_EncodeBlock() (CVE-2026-1... by mborch on Friday November 20, 2026 @04:47AM (#50572392)
Or use defense in depth. There will be a vulnerability in every layer with some non-trivial probability, but rarely in multiple layers at the same time.