Obvious point - the CrowdStrike worldwide IT incident is not the fault of one CrowdStrike staff member.
Whoever created the signature or pushed the button does not operate in isolation. It’s a company with a $73bn market cap.
They need to, later, go back and look at everything that went wrong.
Southwest’s tech debt hurt it back in 2022 but it seems to be doing it some favors today.
Old Windows taketh away, but sometimes old Windows giveth.
https://www.digitaltrends.com/computing/southwest-cloudstrike-windows-3-1/
EDIT: Fix date
EDIT: @peterbutler pushed me to do a little more research, and I’m more comfortable saying it the underlying software probably dates to Windows NT or XP.
The thing I hope is alarming people about today's #CrowdStrike outage is that if the company can take out that much of America's tech infrastructure by accident with a single buggy update, our adversaries can do the same on purpose with a supply-chain attack against CrowdStrike, and that one probably wouldn't be as quick to recover from. #infosec
Let's cut the bullshit and spell out a few things. The IT security industry is about as trustworthy as the food supplement and vitamin industry, but somehow they escaped the same reputation. Their products are overwhelmingly based on flawed ideas, and the quality of their software is exceptionally bad. And while not everyone will agree with the harshness of my words, I'll say this: Essentially everyone in IT security who knows anything in principle knows this.
The sheer volume of CrowdStrike-esque domains being registered and weaponized today is…staggering.
Exploiting An Enterprise Backup Driver For Privilege Escalation - CVE-2023-43896 https://northwave-cybersecurity.com/exploiting-enterprise-backup-software-for-privilege-escalation-part-two
just ran into an incredible bug: portal 2 crashes if you happen to have a CPU with 128 threads
Dear buttplug.io users:
We apologize for the current downtime.
If your butt is BSOD’ing, please try rebooting it a few times.
Just reiterating, because this is getting lost in a lot of the coverage: the original Azure outage and the Crowdstrike Windows bug are NOT related. That said, a significant number of corps run Windows servers on Azure with Crowdstrike Falcon. Wired coverage has more.
https://www.wired.com/story/crowdstrike-outage-update-windows/
So I just happened to read a blog discussing some PoC crashes in Office (https://code610.blogspot.com/2017/10/microsoft-outlook-2016-rwra-crash.html) & what I do? I sent them to @expmon_ immediately (https://pub.expmon.com/analysis/110243/).
ht: I've found real exploitable bugs w/ the power of EXPMON, it's not just a 0day detection system.:)
pour one out for the homies who can't head to the pub tonight because they're stuck unfucking hundreds of computers
Here is a GPO that can apparently run in safe mode to automate the removal of the problematic crowdstrike driver: https://gist.github.com/whichbuffer/7830c73711589dcf9e7a5217797ca617
EDIT: despite my indication that this for running in safe mode, many people seemed to have missed that I said it is for safe mode. So, here is the clarification: IT IS FOR SAFE MODE
H/T @p4gs
When I said "one day my stance on EDR / AV / IPS will be vindicated" I didn't mean for half the Internet to melt down but I am soooooo enjoying this moment.
Thank you #Crowdstrike for giving me my day of glory. Now I will have a story to tell my grandchildren.
so I happen to have a 0day downgrade attack bitlocker bypass, which would be very helpful for people dealing with the crowdstrike issue and have more than about a dozen systems with tpm+secure boot bitlocker lol
the downgrade attack part is why i never publicly documented the original issue yet
also I bet MS are very annoyed that everyone’s saying its their fault