Some bad code just broke a billion Windows machines
Some bad code just broke a billion Windows machines
Cybersecurity firm Crowdstrike pushed an update that caused millions of Windows computers to enter recovery mode, triggering the blue screen of death. Learn ...
There is no learning, companies just move to different antivirus. The new hotness, the cycle repeats over and over until the new antivirus does this same shit. Look at McAfee in 2010, in fact the CEO of Crowdstrike was the CTO of McAfee then. That easily took down millions of windows XP machines.
in fact the CEO of Crowdstrike was the CTO of McAfee then
The hero of Linux adoption then. All hail - what's the name of that guy?
There is learning here.
As companies, we put faith in an external entity with goals not identical to our own: a lot of faith, and a lot of control.
That company had the power to destroy our businesses, cripple travel and medicine and our courts, and delay daily work that could include some timely and critical tasks.
This is not crowdstrike's fault; for the bad code yes, but for the indirect effects of that no. We knew - please tell me we had the brains god gave a gnat and we knew - that putting so much control in the hands of outsiders not concerned or aware of our detailed needs and priorities, was a negligent and foolish thing to do.
The lesson is to do our jobs: we need to ensure we have the ability to make the decisions to which were entrusted, and the power that authority gives us that our decisions when accepted are not threatened by a negligent mistake so boneheaded it's all but the whim of a simpleton. We cannot choose to manage our part of our organization effectively, no matter how (un)important that organization or part is, and then share control with a force that we've seen can run roughshod over it.
It's exactly like the leopards eating our face, except people didn't see they were leopards. No one blames the leopards, as they're just conforming to their nature, eventually.
And no one should blame this company for a small mistake, just because we let the jaws get so close to our faces that we became complacent.
That company had the power to destroy our businesses, cripple travel and medicine and our courts, and delay daily work that could include some timely and critical tasks.
Unless you have the ability and capacity to develop your own ISA/CPU architecture, firmware, OS, and every tool you use from the ground up, you will always be, at some point, “relying on others stuff” which can break on you at a moments notice.
That could be Intel, or Microsoft, or OpenSSH, or CrowdStrike^0. Very, very, very few organizations can exist in the modern computing world without relying on others code/hardware (with the main two that could that come to mind outside smaller embedded systems being IBM and Apple).
I do wish that consumers had held Microsoft more to account over the last few decades to properly use the Intel Protection Rings (if the CrowdStrike driver were able to run in Ring 1, then it’s possible the OS could have isolated it and prevented a BSOD, but instead it runs in Ring 0 with the kernel and has access to damage anything and everything) — but that horse appears to be long out of the gate (enough so that X86S proposes only having Ring 0 and Ring 3 for future processors).
But back to my basic thesis: saying “it’s your fault for relying on other peoples code” is unhelpful and overly reductive, as in the modern day it’s virtually impossible to do so. Even fully auditing your stacks is prohibitive. There is a good argument to be made about not living in a compute monoculture^1; and lots of good arguments against ever using Windows^2 (especially in the cloud) — but those aren’t the arguments you’re making. Saying “this is your fault for relying on other peoples stuff” is unhelpful — and I somehow doubt you designed your own ISA, CPU architecture, firmware, OS, network stack, and application code to post your comment.
——- ^0 — Indeed, all four of these organizations/projects have let us down like this; Intel with Spectre/Meltdown, Microsoft with the 28 day 32-bit Windows reboot bug, and OpenSSH just announced regreSSHion.
^1 — My organization was hit by the Falcon Sensor outage — our app tier layers running on Linux and developer machines running on macOS were unaffected, but our DBMS is still a legacy MS SQL box, so the outage hammered our stack pretty badly. We’ve fortunately been well funded to remove our dependency on MS SQL (and Windows in general), but that’s a multi-year effort that won’t pay off for some time yet.
^2 — my Windows hate is well documented elsewhere.Have you never worked in corporate IT or something? Of course we should blame Crowdstrike, that way we don't get a sev 1 on our scorecard.
Combing over it's Wikipedia article, this company already had a series of other issues.
Sucks to anyone who ever relied on them. Oh look at that, they've been acquiring other security startups and companies. Perhaps that should also be looked into as well?
Are there really a billion systems in the world that run Crowdstrike? That seems implausible. Is it just hyperbole?
I doubt it's too much of a stretch, since even here in australia, we've had multiple airlines, news stations, banks, supermarkets and many others, including the aluminium extrusion business my father works at, all go down, scale this do hundreds of countries with populations tenfold of ours, it puts it into perspective that there may even be more than a billion machines affected
80% of web servers but not 80% of ALL servers, especially in commercial applications.
Sounds pretty plausible to me. An organization doesn’t have to be very big to get into the hundreds or thousands of devices on a network when you account for servers and VM.
A company with 40 employees all accessing and RDS server using a company laptop is looking at 85+ devices already
Yes
Apparently it's embedded in Windows through a specific security option ("Falcon Sensor").
Probably not directly impacting home desktop PCs around the world, and not even most companies running windows, but likely to be active on the big, critical ones.
A billions of computers seems like a lot though.
Whoda thunk automatic updates to critical infrastructure was a good idea? Just hope healthcare life support was not affected.
Many compliance frameworks require security utilities to receive automatic updates. It's pretty essential for effective endpoint protection considering how fast new threats spread.
The problem is not the automated update, it's why it wasn't caught in testing and how the update managed to break the entire OS.
It is pretty easy to imagine separate streams of updates that affect each other negatively.
CrowdStrike does its own 0-day updates, Microsoft does its own 0-day updates. There is probably limited if any testing at that critical intersection.
If Microsoft 100% controlled the release stream, otoh, there'd be a much better chance to have caught it. The responsibility would probably lie with MS in such a case.
(edit: not saying that this is what happened, hence the conditionals)
Hospital stuff was affected. Most engineers are smart enough to not connect critical equipment to the Internet, though.
I’m not in the US, but my other medical peers who are mentioned that EPIC (the software most hospitals use to manage patient records) was not affected, but Dragon (the software by Nuance that we doctors use for dictation so we don’t have to type notes) was down. Someone I know complained that they had to “type notes like a medieval peasant.” But I’m glad that the critical infrastructure was up and running. At my former hospital, we used to always maintain physical records simultaneously for all our current inpatients that only the medical team responsible for those specific patients had access to just to be on the safe side.
I work healthcare adjacent and some providers were affected as expected. Hoping as well that those critical systems were not, but that chance is non zero.
It's because Windows is crap software. Just stop using anything Microsoft makes.
This was very much not caused by windows
Also:
Crowd strike should be held responsible, and with that I don't mean the developmers who were forced to do this shit, I mean the ceo, the CTO.
Jail them.
If you are so critical you better not fuck around and I can guarantee you, they were fucking around, pushing bad practices, etc. why do I say that? Because its lways like that
That comp ay should be dissolved, the C suite jailed.
Also, STOP USING WINDOWS FOR DESKTOP FOR FRACK SAKE. Switch to Linux already, I'm getting tired of having to read this shit.
If you're using windows for servers then you deserve your place right next to those C suite guys and gals
Crowdstrike took Debian and Rocky down earlier this year due to a bad update... Linux is not immune.
And?
Debian is a FREE (as in beer) AND a free (not as in beer but as in freedom) system maintained mainly by volunteers which has an actual focus on us, the end users.
Microsoft, on the other hand, makes us pay through the nose for shit systems that all have focus on Microsoft, NOT on the end user. If you make me pay and spy on me and serve me ads, then at the very fracking least I expect you to take responsibility when you fuck up, and paye for my lost time and money. However, as windows fracks up just about every week, Microsoft would be bankrupt within a month if they'd have to do that.
You make Linux users look bad. Please cease.
Why?
Seriously, why?
Linux is a free system with a fraction of the daily / weekly issues that Microsoft has. Its Been like this for literally decades now.
Microsoft Sella expensive paid systems that spy on us and still feed us advertising. This week, Microsoft and vendors caused likely billions of dollars in damage. Will there be any consequences? Nah. Even better; If I say stip using Microsoft software, I'm a bad guy!
Just a few months ago, it came out that Microsoft consciously decided not to fix critical security hugs resulting in hacks in the US government bu the Chinese government. There was a senate hearing in this where they weally weally promised this time they would behave. I said the same back then, install Linux already and got the same responses, I'm making Linux look bad!
So I ask you.... HOW? How exactly am I the bad guy here, why isn't everyone shitting on Microsoft and it's providers for fucking this up so so wonderfully bad, AGAIN..?
And mind you, we all pay for this shite. Why hasn't anyone there hone to jail for causing shit like this by making decisions that obviously knowingly would cause this shit?
But yeah, you're riiiiight. I make Linux look bad, and we wouldn't want that, now would we?
How about holding an investigation first? You know, just to see where the wrongdoing happened and who actually perpetrated it. (It just might have been a bitter developer or something.)
Also, if people want to use windows, it’s their choice and their consequences. Government and corporate services might do well to consider Linux, but most people don’t even know what a command line is.
If your (large scale) security system is designed properly a bitter developer can't break it. It would take deliberate collusion from multiple people to do so.
Government and corporate services might do well to consider Linux, but most people don’t even know what a command line is.
While this is true, Linux is not the only operating system which is not Windows.
Haiku doesn't require you to do much with CLI.
OpenBSD is Unix with the accompanying culture, but it's just more coherent to the degree that both CLI's are very simple for administration (the way I use my non-work machine, I sometimes think that maybe I should switch ; lacking Wine and games would be an advantage, not a disadvantage) and GUI's to do it have fewer problems than in Linux. NetBSD - a bit more messy, but same as compared to Linux, FreeBSD - even more, but same as compared to Linux. I'm talking about the base system, because X, desktop environments and such are the same.
This doesn't solve the problem of Windows device drivers' support, which is realistically the main thing you'd need for an OS to be popular. Applications are important, but I think if Altera would have a big buyer willing to run Altium on Linux workstations, they'd find in themselves the effort needed make it work in Wine.
But then there was time when ndiswrapper and ndisgen were a thing for Linux and FreeBSD users. Things may have gotten much more complex, but it's a matter of demand.
Because they've done that countless times before and its always the same. A few motbsh ago there was a senate hearing on ehy Microsoft knowingly caused the Chinese government hacking the US government by deciding not to fix critical security bugs to avoid losing contracts and thus,.money.
What is the result, every damn time?
Weeeeewwweee sowweeeyyyy, but the CEO is on it this time! THIS time we won't fuck you over! That was what, a month ago?
Meanwhile I say, fuck Microsoft, stop paying for that corrupt badly built spyware shit, switch to Linux, and then I'm the bad guy.
most people don’t even know what a command line is.
A long time ago, in a galaxy far, far away, Microsoft's consumer OS was command line driven as well. We learned what to do and we managed just fine. Normal people were expected to edit autoexec batch files and configure sound card interrupt settings (children installing games on their parent's PCs figured this out as well). Bring back the elementary school basic computer training classes we had in the 80s and 90s and we're good.
but most people don’t even know what a command line is.
Still with this? Jeez.. that's like saying people probably won't adopt tv today because it's still black and white.
Linux cli is great and many of us use it because of that, but it's been at least 15 years that a regular user would not ever NEED to use it to do anything in linux
Sure, throw people in jail who haven't committed a crime, that'll fix all kinds of systemic issues
As if management even knows what the engineers are doing. lol
Keep dreaming. Maybe next year Linux on desktops will increase by another 0.2% and you can post hundreds of articles about how the “age of Linux” is coming.. again.
"Also, STOP USING WINDOWS FOR DESKTOP FOR FRACK SAKE. Switch to Linux already, I'm getting tired of having to read this shit."
1000% agreed
And for the 451855528th time: switch to Linux already. Why do people keep paying for this shit? Every time I get excuses. I switched to a Linux desktop 20 years ago. There were enout moments that I needed to tweak things to make it work but for the last decade, I haven't had any issues.
If you're dum enough to use windows for servers then you just deserve to burn, if you make that decision then its all on you.
This has nothing to do with Windows or Linux. Crowdstrike has in fact broken Linux installs in a fairly similar way before.
Don’t worry, if it had broken in Linux, these same posters would be railing on CrowdStrike directly, but since it broke on Windows, obviously Microsoft is to blame.