1,415 Microsoft CVEs
One-thousand, four-hundred, and fifteen Microsoft CVEs.
O_O
1,415 Microsoft CVEs
One-thousand, four-hundred, and fifteen Microsoft CVEs.
O_O
pretty sure this breaks Rapid7's ingestion system
woke up abruptly with this on my mind: OM*G they absolutely used copilot or some other agent to write the fixes for all these CVEs.
I'm not one of the performative outragers, but I do read All The Things every day, and there are enough legit well-done studies to show that none of these AI-based "go fix this vuln" systems work as well as advertised.
The patches for a sizeable chunk of these CVEs are gonna have their own CVEs in short order.
@hrbrmstr you ain't seen nothing yet.
@GossiTheDog @hrbrmstr unfortunately they all overflow after 10 and do an RCE
@SteveSyfuhs @GossiTheDog @hrbrmstr what I find amazing is that the majority still seem to be memory safety issues. Out of a sample of 20 of the total, not going to check all of them so I could be wrong :)
@tiraniddo @GossiTheDog @hrbrmstr There absolutely is a pattern you're seeing. What we're observing is the agents are good at finding superficial issues and then backtracking to a POC. They aren't figuring out big picture or the existential stuff. Yet.
@tiraniddo @GossiTheDog @hrbrmstr the fact that it's the same godsdamned memory safety issue in a million places is really just rude.
@hrbrmstr well, today I heard about someone who was let go due to not “using AI enough.”
Create perverse incentives. Get perverse results. :-/
@jarocki O_O