Case 8B99CD · Famous breaches · L3 Applied

Every Windows box is bluescreening

Practise as: Incident drillLevel: L3 Applied

Live alertFriday 19 July 2024, 05:30 UTC: hundreds of Windows servers and laptops are stuck in BSOD boot loops pointing at csagent.sys. Linux and Mac hosts are fine; the service desk is asking if this is a cyberattack.

  1. 01 What happened?
  2. 02 What is the impact?
  3. 03 What do you do?
What a strong answer covers

Try it out loud first. Then check yourself:

  1. Not an attack: a faulty CrowdStrike Falcon content update (Channel File 291) crashed Windows hosts that were online to receive it
  2. Root cause: the sensor expected 21 input fields but the template gave 20, causing an out-of-bounds read in a kernel driver
  3. Fix: boot to Safe Mode or WinRE and delete C-00000291*.sys from the CrowdStrike drivers folder; hosts need BitLocker recovery keys
  4. Prioritise: DCs and the systems that hold BitLocker keys first, then critical services; plan hands-on work at scale
  5. Expect phishing and fake 'fix' scripts riding the outage; Microsoft estimated about 8.5 million Windows devices were affected

If the interviewer pushes back

  • Your BitLocker recovery keys live in AD, and the DCs are also bluescreening. How do you get out of that loop?
  • What should you require from security vendors about staged rollout of content updates that run in the kernel?

More Famous breaches cards

All Famous breaches cards →

cardosec draws a security topic and gives you a clock: explain it out loud with no notes, then see what you covered and what you missed. Free during early access.

Reviewed 2026-10-09