Article Details
Scrape Timestamp (UTC): 2025-09-22 17:10:25.511
Original Article Text
Click to Toggle View
New EDR-Freeze tool uses Windows WER to suspend security software. A new method and proof-of-concept tool called EDR-Freeze demonstrates that evading security solutions is possible from user mode with Microsoft's Windows Error Reporting (WER) system. The technique eliminates the need of a vulnerable driver and puts security agents like endpoint detection and response (EDR) tools into a state of hibernation. By using the WER framework together with the MiniDumpWriteDump API, security researcher TwoSevenOneThree (Zero Salarium) found a way to suspend indefinitely the activity of EDR and antivirus processes indefinitely. Existing EDR disabling methods operate based on the “Bring Your Own Vulnerable Driver” (BYOVD) technique, where attackers take a legitimate but vulnerable kernel driver and exploit it for privilege escalationn. Key drawbacks in the BYOVD attacks include the need to smuggle the driver to the target system, bypass execution protections, and wipe kernel-level artifacts that could expose the operation. EDR-Freeze is described as a much stealthier method that requires no kernel driver, works entirely from the user mode, and leverages legitimate Windows components that are present by default in the operating system. How EDR-Freeze works WerFaultSecure is a Windows Error Reporting component that runs with Protected Process Light (PPL) privileges, designed to collect crash dumps of sensitive system processes for debugging and diagnostic purposes. MiniDumpWriteDump is an API in the DbgHelp library that generates a snapshot (“minidump”) of a process’s memory and state. While doing so, it suspends alll threads of the target process and resumes them after completing the job. EDR-Freeze leverages the WerFaultSecure to trigger MiniDumpWriteDump, which temporarily suspends all threads in the target process while the dump is written. During this process, the attacker suspends the WerFaultSecure process itself, so the dumper never resumes the target, leaving the AV process in a “coma” state. The researcher describes this as a race condition attack that can be reproduced in four steps: The researcher also published a tool that performs these actions, and tested it on Windows 11 24H2, successfully freezing the Windows Defender process. This novel attack chains the intended behavior of both MiniDumpWriteDump and WerFaultSecure, so this is more of a design weakness than a vulnerability in Windows. Defending against EDR-Freeze is possible by monitoring if WER poinnts to the identifier of a sensitive process such as LSASS or security tools. To this purpose, security researcher Steven Lim developed a tool that maps WerFaultSecure to Microsoft Defender Endpoint processes. Still, Microsoft could take steps to harden these Windows components against abuse, like blocking suspicious invocation, only allowing it for certain PIDs, or restricting the possible parameters. BleepingComputer has reached out to Microsoft for a comment on how to defend against such a technique and we will update this post once we hear back. Picus Blue Report 2025 is Here: 2X increase in password cracking 46% of environments had passwords cracked, nearly doubling from 25% last year. Get the Picus Blue Report 2025 now for a comprehensive look at more findings on prevention, detection, and data exfiltration trends.
Daily Brief Summary
Security researcher TwoSevenOneThree introduced EDR-Freeze, a tool leveraging Windows Error Reporting (WER) to suspend security software, bypassing the need for vulnerable drivers.
The method exploits the MiniDumpWriteDump API, which suspends process threads, leaving security agents like EDR tools in a dormant state.
Unlike traditional BYOVD attacks, EDR-Freeze operates entirely from user mode, using legitimate Windows components, enhancing stealth and reducing detection risk.
The technique involves a race condition attack, successfully tested on Windows 11 24H2, freezing the Windows Defender process.
Security measures can include monitoring WER for identifiers of sensitive processes; Microsoft is advised to harden components against such misuse.
The method is considered a design flaw rather than a direct vulnerability, prompting discussions on potential security enhancements.
Microsoft has been contacted for guidance on defending against this technique, with updates pending.