Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2022-24521: Windows CLFS Driver Local Privilege Escalation

Published Apr 15, 2022 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS7.1%94th percentile
CISA KEVYesAdded Apr 13, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2022-24521CWE-20

CVE-2022-24521 is a local privilege-escalation vulnerability in the Microsoft Windows Common Log File System (CLFS) driver. Insufficient validation of crafted base-log metadata permits overlapping structures to corrupt a container-object pointer. One demonstrated exploitation path abuses CClfsBaseFilePersisted::LoadContainerQ and signature encoding/decoding to restore an attacker-controlled pContainer pointer, enabling control of an indirect kernel call. Another observed exploit overlaps client and container contexts to obtain an arbitrary kernel-memory decrement. These primitives can support process-token replacement and escalation to SYSTEM. The vulnerability affected Windows desktop and server releases and was exploited in the wild before its April 2022 patch.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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

A low-privileged local attacker can gain SYSTEM privileges through kernel-memory manipulation and process-token replacement. Demonstrated techniques provide kernel-memory reads and writes or indirect kernel-call control. Exploitation has been observed in ransomware operations, including Cuba and Nokoyawa, as a post-compromise privilege-escalation step.

Mitigation

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

Newer Windows 11 builds restrict kernel-address disclosure and PreviousMode manipulation used by demonstrated exploitation techniques; these restrictions are not a substitute for the security update. Monitor low- or medium-integrity CLFS log manipulation followed by SYSTEM-level activity, suspicious integrity-level transitions, and user-mode access to kernel-memory addresses. No vulnerability-specific workaround is identified.

Remediation

Patch, then assume compromise.

Apply the applicable Microsoft security update released on April 12, 2022, or a superseding update that includes the fix for CVE-2022-24521. The patch adds validation of context offsets, prevents overlap with signature data, and validates context fields. Specific update package identifiers and fixed build numbers are not available here.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
CVE-2022-24521Repository purpose: Proof-of-concept exploit for CVE-2022-24521 (Windows CLFS) implementing a local privilege escalation via crafted BLF (Base Log File) metadata corruption. Structure (11 files): - README.md: minimal build notes (VS2022 v143, C++14) and CVE reference. - Two PoC implementations: - win10_poc/: poc.cpp plus helpers (BlfFileIO.h, ParseBLF.h, CRC32_tool.h). poc.cpp also includes kernel_utils.h and token_operations.h, but those headers are not present in the provided file list (suggesting missing files or incomplete snapshot). - win11_poc/: win11_poc.cpp plus helpers (BlfFileIO.h, ParseBLF.h, CRC32_tool.h, kernel_utils.h). win11_poc.cpp includes pipe_arbitrary_rw.h (not present), implying an additional arbitrary kernel R/W primitive implementation is expected. Core exploit flow (both Win10/Win11 variants): 1) CLFS log setup: deletes any existing container file (MyMiniLog_container_41.clfs), deletes the log name (log:MyMiniLog), then creates/opens the log and adds a 1MB container via CreateLogFile/AddLogContainer. 2) BLF parsing and patching: reads MyMiniLog.blf, locates the first General metadata block (try_find_first_general_block_offset), parses internal offsets/positions (parse_global_variable_positions), then rewrites key fields in the BLF to relocate/copy symbol table data and to set crafted values: - Overwrites SignaturesOffset and symbol table offsets (cbOffset/cbSymName) to move metadata to a controlled location (new_sym_offset=0x2100). - Sets containerContext_cidQueue to 0xFFFFFFFF and containerContext_ullAlignment to a fake vtable pointer (0x50000). - Copies a chunk of metadata from the original symbol table region to the new offset. 3) Integrity repair: recalculates and rewrites CRC32 checksum for the modified block (CRC32_tool.h uses block_offset=0x800 and TotalSectorCount*512 sizing). 4) Memory shaping / gadget setup: - Allocates fixed-address userland memory regions (notably 0x60000, 0x50000, 0xFFFFFFF0) and writes a fake vtable/object layout. - Resolves kernel addresses for SeSetAccessStateGenericMapping (ntoskrnl) and ClfsEarlierLsn (CLFS.SYS) by loading user copies and adding deltas to real kernel module bases obtained via NtQuerySystemInformation. - Uses these as call targets/gadgets in the forged structure. 5) Trigger: re-opens the log (CreateLogFile("log:MyMiniLog", ...)) without adding a container, causing CLFS to parse the crafted BLF/container metadata and hit the vulnerable code path. 6) Privilege escalation: - Win10 PoC: calls ExecuteTokenReplacement(g_PreviousModeAddress) after triggering, implying a write-what-where to flip PreviousMode and then replace token (details depend on missing token_operations.h). - Win11 PoC: uses GetTokenAddresses() to locate current and SYSTEM EPROCESS token fields (build-dependent offset 0x4B8 for >=19041 else 0x358). It then (a) targets a pipe-related kernel address (pipeCtx.attributeValueSizeAddr) to read kernel memory (PKR_ReadKernelMemory), (b) re-triggers with a target of currentTokenPtr to write the SYSTEM token pointer into the current process token field, and finally spawns a new cmd via system("start cmd"). Notable observables / hardcoded values: - CLFS artifacts: log name "log:MyMiniLog", BLF "MyMiniLog.blf", container "MyMiniLog_container_41.clfs". - Fixed virtual addresses used for exploitation: 0x50000 (fake vtable), 0x60000 (fake object), 0xFFFFFFF0 and writes around 0xFFFFFFFF/0x100000007. - Kernel module paths: C:\Windows\System32\drivers\CLFS.SYS and ntoskrnl.exe loaded in userland for symbol offset calculations. Overall: This is operational LPE exploit code (not just detection). It performs on-disk BLF corruption + checksum fix, sets up fake in-memory structures, triggers CLFS parsing, and escalates privileges via token theft/replacement. Some components referenced by includes (token_operations.h, pipe_arbitrary_rw.h, types.h) are not present in the provided content, so full end-to-end compilation may require additional files.uname1able · Disclosed Feb 19, 2026 · cpp · c++ · localOperational
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 1909operating_system
Microsoft CorporationWindows 10 20h2operating_system
Microsoft CorporationWindows 10 21h1operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 11 21h2operating_system
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows 8.1operating_system
Microsoft CorporationWindows Rt 8.1operating_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
Microsoft CorporationWindows Server 20h2operating_system
FAQ

Frequently asked questions

Is CVE-2022-24521 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Apr 13, 2022.
Is there a public exploit for CVE-2022-24521?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2022-24521, the earliest disclosed Feb 19, 2026.
Is there a patch for CVE-2022-24521?
Apply the applicable Microsoft security update released on April 12, 2022, or a superseding update that includes the fix for CVE-2022-24521. The patch adds validation of context offsets, prevents overlap with signature data, and validates context fields.
What products are affected by CVE-2022-24521?
Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 1909, Microsoft Corporation Windows 10 20h2, and at least 15 more.
How severe is CVE-2022-24521?
CVE-2022-24521 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 7.1% (94th percentile) as of Oct 16, 2026.
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence5Every report linking this CVE to a named adversary.
Associated malware5Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.