BrianKrebs (@[email protected])
infosec.exchange
Attached: 1 image This is fitting. The top topic on Xitter right now is of course the global Crowdstrike/Windows clusterfuck. But the AI summary of the discussion is hilarious, b/c it summarizes a bunch of sarcastic posts and makes it sound like a positive (or at least can-do) story.

The machines, now inaccessible, are arguably more secure than before.

    • Sailor Sega Saturn@awful.systemsEnglish
      0·
      2 months ago

      Fair warning that I’ll be ranty because I hate losers talking about DEI hires.

      So why is memory address 0x9c trying to be read from? Well because… programmer error.

      So what happened is that the programmer forgot to check that the object it’s working with isn’t valid, it tried to access one of the objects member variables…

      This is a huge assumption. The last rumor I’ve read from actual cybersecurity people is that Crowdstrike’s update files were corrupt (update: disproven by Crowdstrike’s blog post). If this is true it’s likely still from programmer error at some level, but maybe not as simple as “whoopsie I forgot an if (data == nullptr) teehee”.

      He, like the rest of us that don’t work at Crowdstrike, has no idea what happened. I have seen computers do the weirdest gosh darn things. I know better than to assume anything at this point. I wouldn’t even rule out weird stuff like the data getting corrupted between release qualification and release yet.

      It turns out that C++, the language crowdstrike is using, likes to use address 0x0 as a special value to mean “there’s nothing here”, don’t try to access it or you’ll die.

      This thread is full of these sorts of small technical inaccuracies and oversimplifications so I won’t point out all of them, but nothing in the C++ standard requires null pointers to refer to memory address 0x0. Nor does it require that dereferencing a null pointer terminates the program.

      Windows died not because C++ asked it nicely to, but because a driver tried to access an address which wasn’t paged in.

      Crowdstrike should have set up automated testing using address sanitizer and thread sanitizer that runs on every code update.

      The funny thing about accessing into non-paged memory in kernel space:

      1. It will crash regardless of if it’s running under Asan or not, sanitizers are literally irrelevant based on what we know so far
      2. The Asan version he linked to is for user-space. In the windows kernel you’d need KASAN instead.

      (If this was a simple nullptr dereference on bad input data then perhaps a fuzzer would have helped. Fuzzers are great though I have no idea how hard they are to use with kernel drivers)

      C++ is hard. Maybe they have a DEI engineer that did this

      Dude would probably call me a “DEI hire”; but I bet I could beat him in a C++ deathmatch so neener neener.

      • V0ldek@awful.systemsEnglish
        0·
        2 months ago

        Also, and this shouldn’t be left unsaid, we’re talking about the Windows kernel here. A place with C++ code so cursed it is legendarily unhealthy to work in, as the cosmic horrors contained within slowly eat away at your sanity and warp the perception of time and space. Seeing that code for a few hours is enough to make a grown man cry. Seeing that code for a few weeks is enough to make you never cry again, as the terrible truth worms its way into your mind.

        “DEI hire”, hah! The creature makes no distinction for race or gender as it fattens itself upon your failure! Even a glimpse at the edge of its abyss is enough to trigger a cycle of revelation - all modern software lies upon a rotting pile of ancient mistakes.