CVE-2023-36900 is an elevation of privilege vulnerability in the Windows Common Log File System (CLFS) driver. The flaw affects a privileged Windows kernel component responsible for log file services. Specific technical details about the vulnerable code path or function are not available in the provided information, but successful exploitation would allow an attacker to elevate privileges on a vulnerable Windows system.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept (POC) exploit for CVE-2023-36900, a vulnerability in the Microsoft Windows CLFS.sys driver that can be triggered by manipulating .blf log files. The exploit is designed to cause a denial-of-service (BSOD) on vulnerable Windows systems. The repository includes: - Python scripts (poc/launch.py, poc/update_crc32.py) to automate the creation, manipulation, and corruption of .blf log files. The scripts adjust internal structures and CRC32 checksums to craft a file that will trigger the vulnerable code path in CLFS.sys. - C++ source code for utilities to create and interact with log files (c_sources/), including creating logs, streams, and opening logs using both documented and native Windows APIs. - A detailed writeup (writeup/eng/writeup_eng.md) explaining the vulnerability, the patch, and the exploitation process, including the required changes to the .blf file to reach the vulnerable code path. - An ImHex pattern file (imhex_pattern/blf_clfs.hexpat) for analyzing .blf files. The exploit is local and requires the attacker to have the ability to run code and manipulate files on the target system. The main attack vector is through local file manipulation and execution of crafted binaries/scripts. The repository is structured with clear separation between the POC scripts, C++ utilities, and documentation, making it a comprehensive resource for understanding and reproducing the exploit for CVE-2023-36900.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.