A bit of both. And a dash of general cheapness, too.
AI, for all the bad, is able to quickly exploit flaws. Mostly already known ones. Admins are not always keeping things up to date, when there’s even a admin. Infrastructure is badly done, having gaping open doors that only asks for someone to enter. Competent people all around, able to detect, act, and fix, are removed because who needs this.
AI, like all computer programs, is really good at being persistent.
From the beginning of computer programming, the ability to engage in loops to exhaust every possibility was always going to be faster and more comprehensive than what humans could, or were willing to do. You could naively try every combination for cracking PINs. Then came more sophisticated loops that would try every combination by first going through known password patterns (common dictionary words, common numerical combinations, etc.). There were rainbow tables computed to where certain computationally expensive processes could be pre-computed before a leak so that a leak of hashed passwords could be more quickly exploited.
And there are tools scanning the web for all sorts of known vulnerabilities, being much more comprehensive and systematic. If you have a vulnerable machine exposed to the internet, an automated hacker might compromise it.
The current state of AI-assisted hacking includes tools for analyzing patches and CVEs to reverse engineer exploits for unpatched machines. So everyone is now in a hurry to apply patches as soon as they come out, lest they be left behind as hackers adapt their scripts to keep crawling for recently patched vulnerabilities.
Plus there are more tools for searching for vulnerabilities, either in code or at some sort of other attack surface. The number of vulnerabilities being patched right now is pretty high, which puts just higher pressure on all of the processes to more aggressively develop quick patches for known vulnerabilities, install patches as soon as possible after release, etc.
Throw in an ecosystem where programmers might have been laid off, or teams are understaffed, or using AI tools themselves and have less of a firm grasp on their own codebase, and that’s just a recipe for less reliability.
A generalized estimation is that for every 100 lines of bug there is a possible exploit waiting to be leveraged. Linux Kernel alone is over 40 million lines. Good Luck!
That said, I do hope that these LLM assists patches are closing these and not introducing new ones. But I am not too optimistic about that. :)
Are we really though? Or is it just crap code.
Mostly just crap code and/or shitty corporate IT management.
A bit of both. And a dash of general cheapness, too.
AI, for all the bad, is able to quickly exploit flaws. Mostly already known ones. Admins are not always keeping things up to date, when there’s even a admin. Infrastructure is badly done, having gaping open doors that only asks for someone to enter. Competent people all around, able to detect, act, and fix, are removed because who needs this.
AI, like all computer programs, is really good at being persistent.
From the beginning of computer programming, the ability to engage in loops to exhaust every possibility was always going to be faster and more comprehensive than what humans could, or were willing to do. You could naively try every combination for cracking PINs. Then came more sophisticated loops that would try every combination by first going through known password patterns (common dictionary words, common numerical combinations, etc.). There were rainbow tables computed to where certain computationally expensive processes could be pre-computed before a leak so that a leak of hashed passwords could be more quickly exploited.
And there are tools scanning the web for all sorts of known vulnerabilities, being much more comprehensive and systematic. If you have a vulnerable machine exposed to the internet, an automated hacker might compromise it.
The current state of AI-assisted hacking includes tools for analyzing patches and CVEs to reverse engineer exploits for unpatched machines. So everyone is now in a hurry to apply patches as soon as they come out, lest they be left behind as hackers adapt their scripts to keep crawling for recently patched vulnerabilities.
Plus there are more tools for searching for vulnerabilities, either in code or at some sort of other attack surface. The number of vulnerabilities being patched right now is pretty high, which puts just higher pressure on all of the processes to more aggressively develop quick patches for known vulnerabilities, install patches as soon as possible after release, etc.
Throw in an ecosystem where programmers might have been laid off, or teams are understaffed, or using AI tools themselves and have less of a firm grasp on their own codebase, and that’s just a recipe for less reliability.
Yep, we now ave a setup that is the worst of all possibilities.
Absolutely agree. It’s basically a fuzzer with a big database of exploits. Of course it can find exploits.
It’s one area it makes sense to me, but I’m pretty sure you could do even better with a specifically trained model rather than a general LLM.
Regardless, you still need buggy code to exploit.
Hasn’t that always been a near-unlimited resource though?
AI has led it to a previously unthinkable level of buggy code.
A generalized estimation is that for every 100 lines of bug there is a possible exploit waiting to be leveraged. Linux Kernel alone is over 40 million lines. Good Luck!
That said, I do hope that these LLM assists patches are closing these and not introducing new ones. But I am not too optimistic about that. :)