I feel like the current situation is temporary. LLMs are finding all the bugs. LLMs are also help fixing most of the bugs. Once most of the bugs are fixed, LLMs should be good at finding bugs before shipping them, the stream of bug reports will die down, and we'll be back to vulnerabiltiy reports being special. Further, the fact that bugs are so easy to find by LLMs means there is strong incentives to find ways to mi…
That supposes that LLMs can write secure software. Also, if we assume that finding bugs is easier that not creating them (reasonable I would say), the supply of bugs will never be exhausted.
Vulnerability reports are not special anymore
231–240 of 249 posts
Re: Vulnerability reports are not special anymore
#232Earlier quoted context omitted.
That supposes that LLMs can write secure software. Also, if we assume that finding bugs is easier that not creating them (reasonable I would say), the supply of bugs will never be exhausted.
How can it be easier to find them than to not create them? Whatever you do to find them, you could do before you release.
Especially if you use AI, let's say you have it implement a feature and then change your mind. In my experience AI makes as many if not more bugs than a human.
Re: Vulnerability reports are not special anymore
#233Earlier quoted context omitted.
Will xorg backport patches from Xlibre?
No, because xorg is a dead project that doesn't take any patches from anywhere and xlibre has shit code quality and is probably vibecoded now
Re: Vulnerability reports are not special anymore
#234Earlier quoted context omitted.
Vulnerability reports are a voluntary service to help a vendor or software project. It’s often an annoyance for the security researcher. I understand people are getting slammed and it sucks, but the main result of rejecting them is going to be an increase in full disclosure. As a note: if you have a bug (that isn’t devastating but you’d like to talk about) having an LLM write up the disclosure is a great way to check…
> I understand people are getting slammed and it sucks, but the main result of rejecting them is going to be an increase in full disclosure. Right, what I'm saying is that letting those bugs go to full disclosure (aka being filed as public issues, like every other bug) would have been a significant damage to user safety a year ago, and it's not anymore.
Re: Vulnerability reports are not special anymore
#235Earlier quoted context omitted.
Its been like that for half a decade across all software. People act like finding a linux kernel bug is a big deal, completely ignoring the fact that in order to exploit that bug, the attacker has to be able to run code on your computer in the first place, which is extremely hard to do these days remotely. Also people ironically just DGAF that much. The last actual bad exploit was log4shell in java, which given how i…
Ah yes, just move away from all apache libraries, should only take a day or two.
Re: Vulnerability reports are not special anymore
#236Earlier quoted context omitted.
Its been like that for half a decade across all software. People act like finding a linux kernel bug is a big deal, completely ignoring the fact that in order to exploit that bug, the attacker has to be able to run code on your computer in the first place, which is extremely hard to do these days remotely. Also people ironically just DGAF that much. The last actual bad exploit was log4shell in java, which given how i…
These bugs are indeed important, you need them once you‘ve found a bug in an application.
Re: Vulnerability reports are not special anymore
#237Earlier quoted context omitted.
> First, this is great reply with lots of real world experience to share. I know how they came about with this setup, but I think that's the wrong way of approaching the problem. Their problem is legacy and trickle-in features in an otherwise unmaintainable code. With AI, they can rewrite their software to minimize dependencies and in general reduce the attack surface by allowing the business to automate more on thei…
Of course, all the generated code has to reviewed and vetted for by a senior developer. Of course, this has to be re-done every now and then when new classes of vulnerabilities appear that the previous generation didn’t have in mind. Or do you just trust the AI that was trained on a lot of bogus code?
Re: Vulnerability reports are not special anymore
#238Earlier quoted context omitted.
Yeah I completely understand their intent, but I might get 30 vulnerabilities across a multiple repos flagged in a week. It is already tedious to check them all and assess if they're worth worrying about let alone having to update them. These are 99% Javascript though - I suspect other ecosystems are much more manageable.
I unironically think the solution is vibecoding your own Javascript blobs that use no frameworks and have no (or minimal) external dependencies. At this point it is entirely feasible for many kinds of projects.
Re: Vulnerability reports are not special anymore
#239Earlier quoted context omitted.
Yep, I've updated dependencies with an RCE that can't be exploited in my codebase just to keep my security team happy. Not worth the multiple arguments about it not actually being an issue.
You can never guarantee that the codepath of a dependency that is vulnerable can not be reached or used as a gadget in an exploit chain. Patching dependencies, even when no direct vulnerability arises is an essential part of defense in depth and sevurity hygene.
Re: Vulnerability reports are not special anymore
#240"LLMs are as good as almost any security researcher" Oh really? If LLMs were as good as almost any security researcher then you wouldn't be getting flooded by bullshit reports from them. You'd be receiving legitimate reports instead.