Identity and security · CrowdStrike
CrowdStrike Falcon Channel File 291 content update crashes Windows hosts
- Started
- Jul 19, 2024, 04:09 UTC
- Duration
- Not published
- Affected
- CrowdStrike Falcon sensor for Windows (version 7.11 and above), Windows hosts running the sensor
- Cause
- Final reviewA Rapid Response Content update delivered through Channel File 291 introduced a matching criterion for a 21st input field, while the sensor code supplied only 20 inputs. The Content Interpreter read past the end of its input array and crashed Windows hosts. A logic error in the Content Validator let the content through, and the content was not deployed in stages.
- Was it an attack?
- No, per the provider or investigators
- State
- monitoring
Anatomy
1. Trigger
Policy or data push
2. Already broken
Latent bug, Missing validation
3. What made it spread
Global configuration propagation
4. Blast radius
global: Global
5. Cause category
Change or deployment
Labels follow the root-cause taxonomy. A person's change is recorded as the trigger and the missing safeguard as what was already broken; “human error” is never a cause here.
How the explanation changed
July 19, 2024 · Preliminary cause
“The outage was caused by a defect found in a Falcon content update for Windows hosts. Mac and Linux hosts are not impacted. This was not a cyberattack.”
July 24, 2024 · Preliminary cause
“On July 19, 2024, two additional IPC Template Instances were deployed. Due to a bug in the Content Validator, one of the two Template Instances passed validation despite containing problematic content data.”
August 6, 2024 · Final review
“The new IPC Template Type defined 21 input parameter fields, but the integration code that invoked the Content Interpreter with Channel File 291’s Template Instances supplied only 20 input values to match against.”
CrowdStrike External Technical Root Cause Analysis, Channel File 291 (2024-08-06)
What the provider committed to change
- Validate the number of input fields in the Template Type at sensor compile time
- Add runtime input array bounds checks to the Content Interpreter for Channel File 291
- Add checks to the Content Validator so matching criteria cannot exceed the inputs provided
- Test every new Template Instance, not only the initial one
- Staged deployment of Template Instances through canary and successive rings with bake-in time
- Customer control over where and when Rapid Response Content is deployed
- Two independent third-party reviews of sensor code and the end-to-end quality process
Impact, as reported
- Windows devices affected: 8.5 million, less than one percent of all Windows machines, according to Microsoft estimate (Microsoft: Helping our customers through the CrowdStrike outage (2024-07-20)).
Every figure is attributed to whoever stated it. Crowd reports are labelled user reports and never treated as users affected.
Attack or not
“The outage was caused by a defect found in a Falcon content update for Windows hosts. Mac and Linux hosts are not impacted. This was not a cyberattack.”
George Kurtz, CrowdStrike Founder and CEO (letter sent 2024-07-19 19:30 UTC, as reproduced on the hub), July 19, 2024 (CrowdStrike Remediation and Guidance Hub (CEO statement))
Post-incident reviews
- Preliminary review, July 24, 2024
- Final review, August 6, 2024
Sources
- CrowdStrike External Technical Root Cause Analysis, Channel File 291 (2024-08-06) (provider, read November 17, 2026)
- CrowdStrike Preliminary Post Incident Review (2024-07-24) (provider, read November 17, 2026)
- CrowdStrike Remediation and Guidance Hub (CEO statement) (provider, read November 17, 2026)
- CrowdStrike blog: Channel File 291 RCA is available (2024-08-06) (provider, read November 17, 2026)
- Microsoft: Helping our customers through the CrowdStrike outage (2024-07-20) (provider, read November 17, 2026)
Last verified November 17, 2026. Spot an error? The methodology page says how corrections work.