news.mlab.sh
Back to the feed
threat-intel

Nightmare-Eclipse Strikes Again with 'ShieldCrash' Windows Exploit

HighCVSS 7.8
Summary

Nightmare-Eclipse, a security researcher, has released another Windows zero-day exploit, 'ShieldCrash,' which bypasses a previous patch and allows for privilege escalation. Despite Microsoft's patching efforts, the researcher claims the vulnerability remains exploitable, highlighting a recurring weakness in how Microsoft addresses its security flaws. This ongoing feud with Microsoft underscores the need for organizations to proactively monitor Defender intelligence updates and implement robust security measures beyond simply patching Windows Defender.

Nightmare-Eclipse, a security researcher known for their ongoing vendetta against Microsoft, has released 'ShieldCrash,' a new zero-day exploit for Windows. This exploit bypasses a previous patch and enables privilege escalation, allowing an attacker to read arbitrary files under the SYSTEM security context. The exploit follows a pattern of the researcher releasing new vulnerabilities shortly after Microsoft’s patch releases for previous exploits, such as ShieldBreak, which was a bypass for Microsoft’s patches against RoguePlanet.

Nightmare Eclipse claims that despite Microsoft’s patching efforts, the vulnerability remains exploitable, suggesting a deeper issue with how Microsoft addresses its security flaws. "ShieldCrash" is a race condition bug that allows an adversary to read arbitrary files under the SYSTEM security context on fully patched Windows systems. The researcher claims that this is not simply an arbitrary file read, but a full privilege escalation.

Dark Reading contacted Microsoft for comment, but the company did not respond. John Strand, owner of Black Hills Information Security, described the situation as "petty" on both sides, emphasizing the need for collaboration rather than conflict. Ensar Seker, CISO at SOCRadar, notes that the ability to bypass successive fixes for RoguePlanet and ShieldBreak indicates a need for a more comprehensive redesign of the underlying security boundary.

Despite not providing full SYSTEM shell or arbitrary write capabilities, the exploit still poses a significant threat. It could expose highly sensitive files, including configuration data and credentials, which ordinary users cannot access. This privileged file disclosure can become a key component of a larger attack chain. Organizations should not disable Windows Defender due to concerns about its security; instead, they should closely monitor Microsoft’s guidance and Defender intelligence updates, enable tamper protection, restrict local execution and administrative access, and hunt for suspicious processes interacting with protected files through Defender-related mechanisms.

Because the exploit code is now publicly available, defenders should expect attackers to utilize it for malicious activities such as credential theft, persistence, and full privilege escalation. Microsoft should also assess the complete vulnerability class and related code paths, not only the specific condition demonstrated by this latest proof of concept.

Read the full article at Dark Reading