Be me.
Have old server running a PHP app.
Try to upgrade to patch PHP bug.
Server still running Ubuntu 16.04 LTS.
oops.jpg
Upgrade to at least 22.04 LTS for now.
Takes hours.
PHP upgraded along the way. Good.
Try to restart server.
Won't start.
Config still using references to PHP FPM 7.0.
Update config.
Server starts.
Woo!
Try app.
App not working.
App also outdated, using old version that doesn't support PHP 8.
cry.gif
My concern with the upcoming PHP RCE disclosure is how many systems could remain exposed long after patches become available.
Roughly a third of PHP websites still run PHP 5 or 7. Some operators will need to migrate old applications before they can move to a supported release. Even on supported versions, plenty of systems won't be patched immediately. Some owners won't notice the advisory; others can't deploy an update that quickly.
We still need the technical details to understand the actual exposure. If reliable, unauthenticated exploitation works across common deployments, I'd expect automated mass exploitation very quickly. AI-assisted exploit development and payload adaptation could shorten the response window further.
For detection teams, I'd prepare now for the activity that follows. I expect plenty of familiar shells, downloaders, webshells and persistence mechanisms, even though the entry point is new.
I've published a process-watcher guide with PHP configurations to record descendant processes and their command lines, with optional termination rules for shells, interpreters and known payload patterns:
https://t.co/7nluFV3Q25
Short-lived commands can still be recorded, even when they finish before the kill response arrives. Activity entirely inside the PHP worker remains a blind spot.
THOR Lite already includes relevant detections. We'll also review internally what additional post-exploitation coverage we can make publicly available.
After patching, check for compromise. An update doesn't remove an existing webshell or invalidate stolen credentials.
Chronic illness recovery and bad mental health combo took me out for 12 hours. Twelve hours to "recover" enough energy to be somewhat human sucks. Someone reboot my nerve system please.
@techspence Protected users tripped me up recently doing some decommissioning of a on prem Citrix environment. Still learning even when ripping it down.
This is the fastest way I’ve found to fix an IT problem. have the user try to reproduce it while you’re watching.
60% of the time, it fixes itself every time.
Sure, this app hates me, but where else can you see a Ukrainian drone manufacturer trolling Russian internet executives after blowing up their data centers?