Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

Windows Common Log File System Driver Elevation of Privilege Vulnerability

IdentifiersCVE-2023-28252CWE-269

CVE-2023-28252 is an elevation-of-privilege vulnerability in the Windows Common Log File System (CLFS) driver. Microsoft described it as a post-compromise flaw in CLFS.sys that can be exploited after an attacker has already obtained code execution on a target system. Successful exploitation allows the attacker to elevate privileges to NT AUTHORITY\SYSTEM. The provided content does not include the specific vulnerable function or root-cause details for this CVE, but it does establish that the issue affects the Windows CLFS driver, was patched in Microsoft’s April 2023 Patch Tuesday, carried a CVSS v3 score of 7.8, and was reported by Microsoft as exploited in the wild as a zero-day. The vulnerability has also been referenced in reporting on ransomware intrusions, including Akira and Storm-0506 activity, as a local privilege-escalation step following initial access.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation provides local privilege escalation to SYSTEM on a vulnerable Windows host. In practical intrusion chains, this can convert an initial foothold or low-privileged execution context into full local administrative control, enabling credential theft, defense evasion, persistence, lateral movement, and broader domain compromise. The content also states the vulnerability was exploited in the wild as a zero-day and has been used in ransomware-related operations, underscoring its operational value after initial compromise.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by limiting opportunities for post-compromise local code execution and privilege escalation: restrict local and remote access to trusted users, minimize the presence of low-privileged interactive accounts, harden systems against initial compromise, and monitor for suspicious post-exploitation behavior associated with CLFS abuse and privilege-escalation activity. Because this is a local EoP vulnerability, compensating controls should focus on preventing initial access, detecting malicious execution on hosts, and containing compromised accounts and endpoints until patches can be applied.

Remediation

Patch, then assume compromise.

Apply Microsoft’s April 2023 security updates that address CVE-2023-28252. Because the flaw is in the Windows CLFS driver and was fixed as part of Patch Tuesday, remediation is to deploy the relevant cumulative/security updates for affected Windows systems and verify patch compliance across endpoints and servers.
PUBLIC EXPLOITS

Exploits

3 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).

VALID 3 / 4 TOTALView more in app
CVE-2023-28252MaturityPoCVerified exploit

This repository contains a functional local privilege escalation exploit for CVE-2023-28252, a vulnerability in the Windows Common Log File System (CLFS) driver (CLFS.sys). The exploit is implemented in C++ and is designed to run on Windows 10/11 (21H2/22H2) and Windows Server 2022 with vulnerable versions of CLFS.sys. The exploit works by crafting and manipulating .blf log files and leveraging kernel memory operations to overwrite the process token, thereby granting SYSTEM privileges to the attacker. The main entry point is 'clfs_eop/clfs_eop.cpp', which orchestrates the environment setup, kernel address discovery, file crafting, and the actual privilege escalation. The exploit does not require network access and must be executed locally. The repository includes supporting headers and Visual Studio project files, but the core logic resides in the C++ source files. No external endpoints are targeted; the attack is purely local, focusing on the CLFS.sys driver and associated log files.

fortraDisclosed Jun 27, 2023c++local
CLFSMaturityPoCVerified exploit

This repository contains a working local privilege escalation exploit for CVE-2023-28252, a vulnerability in the Microsoft Windows Common Log File System (CLFS) driver (CLFS.SYS). The main exploit logic is implemented in C++ (lib/clfs_eop.cpp and lib/clfs_eop.h), with supporting project files for Visual Studio. The exploit works by manipulating kernel memory structures via the CLFS driver to obtain a SYSTEM token, thereby elevating the attacker's privileges to SYSTEM. The code includes logic for kernel address discovery, pipe spraying, and direct system calls to achieve the exploit. The repository also includes two simple VBScript files (encrypt.vbs and decrypt.vbs) for text encoding/decoding, which are unrelated to the main exploit. The exploit targets multiple versions of Windows 10, Windows 11, and Windows Server (2016, 2019, 2022) as specified in the header comments. The attack vector is local, requiring the attacker to execute code on the target system. The main fingerprintable endpoint is the CLFS.SYS driver file. The exploit is operational and provides SYSTEM-level access if successful.

byt3n33dl3Disclosed Mar 21, 2024c++vbscriptlocal
CVE-2023-28252-Compiled-exeMaturityPoCVerified exploit

This repository contains a C++ implementation of a local privilege escalation exploit for CVE-2023-28252, targeting the Windows Common Log File System (CLFS) driver (clfs.sys). The exploit is based on Fortra's original proof-of-concept and is modified to allow the user to specify an arbitrary binary to execute as SYSTEM after successful exploitation. The main code is in 'clfs_eop/clfs_eop.cpp', with supporting headers and Visual Studio project files. The exploit works by manipulating kernel memory structures via the vulnerable driver, ultimately replacing the current process token with a SYSTEM token and then executing the specified payload. The exploit is operational and can be used to run any command or binary as SYSTEM on affected Windows versions. The only fingerprintable endpoint is the path to the vulnerable driver. The repository is well-structured for building with Visual Studio and includes both source and project files.

duck-secDisclosed Jan 22, 2024cpphlocal
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 20h2operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 21h2operating_system
Microsoft CorporationWindows 11 22h2operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2008 R2operating_system
Microsoft CorporationWindows Server 2008 Sp2operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence1

Every observed campaign linking this CVE to a named adversary.

Associated malware4

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1

Community discussion across Reddit, Mastodon, and other social sources.