Heap-based buffer overflow in Windows Common Log File System Driver
CVE-2024-49138 is a heap-based buffer overflow in the Windows Common Log File System (CLFS) driver that allows a locally authenticated, low-privileged attacker to elevate privileges to SYSTEM. It affects supported Windows client and server versions at the time of disclosure in December 2024. A proof-of-concept tested on Windows 11 23H2 demonstrated arbitrary kernel memory read/write and process-token replacement to obtain a SYSTEM shell. The vulnerability was actively exploited before Microsoft released a fix in its December 2024 security updates.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation grants SYSTEM privileges and full access to the affected Windows system. Demonstrated exploitation provides arbitrary kernel memory read/write and permits replacement of the attacking process's security token with a SYSTEM token.
If you can’t patch tonight, do this now.
If immediate patching is not feasible, reduce opportunities for local post-compromise exploitation by minimizing untrusted code execution on endpoints, restricting user ability to obtain or retain local access, enforcing least privilege, and closely monitoring for anomalous behavior involving CLFS and unexpected privilege transitions. Additional defensive measures include hardening endpoint protections, limiting execution from untrusted locations, and increasing detection coverage for suspicious kernel-level privilege escalation activity. These measures are compensating controls only and do not remove the underlying flaw.
Patch, then assume compromise.
Install the applicable Microsoft December 2024 security updates addressing CVE-2024-49138 on affected Windows client and server systems, including affected Windows ESU installations. Prioritize deployment because exploitation has been observed in the wild.
3 exploits validated by Mallory's analysis. Hidden: 11 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.