…according to a Twitter post by the Chief Informational Security Officer of Grand Canyon Education.

So, does anyone else find it odd that the file that caused everything CrowdStrike to freak out, C-00000291-
00000000-00000032.sys was 42KB of blank/null values, while the replacement file C-00000291-00000000-
00000.033.sys was 35KB and looked like a normal, if not obfuscated sys/.conf file?

Also, apparently CrowdStrike had at least 5 hours to work on the problem between the time it was discovered and the time it was fixed.

  • tiramichu@lemm.ee
    link
    fedilink
    English
    arrow-up
    5
    ·
    4 months ago

    You’re right of course and that should be on Microsoft to better implement their driver loading. But yes.

    • Morphit @feddit.uk
      link
      fedilink
      English
      arrow-up
      8
      ·
      4 months ago

      The driver is in kernel mode. If it crashes, the kernel has no idea if any internal structures have been left in an inconsistent state. If it doesn’t halt then it has the potential to cause all sorts of damage.