Oct 21, 2026 · 40 min · 12 segments
We put together a special Wednesday CyberCall after two critical PHP vulnerabilities, known as php2shell, leaked a day before their planned disclosure…
Andrew MorganHost
John HammondGuestBut I think that everybody that's listening to the show, we need to answer a couple of additional questions, right? The first question that we need to answer is what does our rapid patching process look like? because that's now the normal patching process.
If you think you have a couple of days, if you think that you have like a week to push patches out, that ain't gonna happen.
We're already patch diffing it and coming up with POC exploit code at our continuous pen testing practice.
uh it's not something unless you know what it's doing and you know what you're doing it could do something else but the point i'm trying to get at is the time frame that we had a year ago, year and a half ago, is gone.
As soon as these things hit, the security community and the attack community are patch-diffing this.
I can take a binary that is patched and that vulnerability has been addressed, and I can look at the differences between those two to try to identify where in the code the vulnerability is.
Whenever they patch an executable, it makes hundreds of different changes to that executable.
With AI, it can grind through that stuff way faster than we ever could do a year and a half before.
But I think when we saw a lot of the panic yesterday and into the evening, into the early morning, is when folks were trying to make sense of this, you had nerds and geeks and security researchers, again, trying to guess at what is this going to be because of the odd disclosure timing with the actual release and patches coming out this morning.
Last night, folks who are just trying to figure out what is the vulnerability? Can I recreate a proof of concept? Can I figure it out just from what we're seeing in changes in the GitHub and the source code? And some folks were fine in one angle.
Turns out it would be just one of the two or even potentially other new things that they're exploring.
But I think that everybody that's listening to the show, we need to answer a couple of additional questions, right? The first question that we need to answer is what does our rapid patching process look like? because that's now the normal patching process.
If you think you have a couple of days, if you think that you have like a week to push patches out, that ain't gonna happen.
We're already patch diffing it and coming up with POC exploit code at our continuous pen testing practice.
uh it's not something unless you know what it's doing and you know what you're doing it could do something else but the point i'm trying to get at is the time frame that we had a year ago, year and a half ago, is gone.
As soon as these things hit, the security community and the attack community are patch-diffing this.
I can take a binary that is patched and that vulnerability has been addressed, and I can look at the differences between those two to try to identify where in the code the vulnerability is.
Whenever they patch an executable, it makes hundreds of different changes to that executable.
With AI, it can grind through that stuff way faster than we ever could do a year and a half before.
But I think when we saw a lot of the panic yesterday and into the evening, into the early morning, is when folks were trying to make sense of this, you had nerds and geeks and security researchers, again, trying to guess at what is this going to be because of the odd disclosure timing with the actual release and patches coming out this morning.
Last night, folks who are just trying to figure out what is the vulnerability? Can I recreate a proof of concept? Can I figure it out just from what we're seeing in changes in the GitHub and the source code? And some folks were fine in one angle.
Turns out it would be just one of the two or even potentially other new things that they're exploring.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.