CrowdStrike "FalconFlank" Zero-Day: Local Privilege Escalation & EDR Tampering via Named Pipe Race Condition
Technical analysis of the CrowdStrike Falcon Sensor FalconFlank zero-day flaw: named pipe race condition, token duplication, and EDR defense evasion.
Security researchers have disclosed a local privilege escalation zero-day flaw named "FalconFlank" in the CrowdStrike Falcon Sensor for Windows, allowing low-privileged local users to exploit inter-process communication named pipes to hijack SYSTEM tokens and tamper with sensor telemetry.
Zero-Day (Disclosed as FalconFlank) (CWE-362 / CWE-250: Race Condition & Execution with Unnecessary Privileges)
Severity: High (CVSS 7.8 (Local SYSTEM Escalation))
Status: 🚨 Public Disclosure / Vendor Advisory In-Progress
Affected Systems: CrowdStrike Falcon Sensor Windows Agent versions prior to 7.18+
Anatomy of the Named Pipe Race Condition
FalconFlank exploits a timing window during local sensor IPC initialization. A non-privileged attacker continuously connects to the Falcon named pipe endpoint, impersonating a legitimate diagnostic client. By winning the race condition during token validation, the attacker duplicates the sensor's NT AUTHORITY\SYSTEM handle, granting full administrative and kernel interface control.
Defensive Guidance
- Update Falcon Sensor Agents: Deploy the latest sensor build issued by CrowdStrike.
- Audit Local Administrative Accounts: Ensure strict local privilege separation on all Windows endpoints to restrict attacker staging capability.