Loading vulnerability…
An information disclosure vulnerability in the Windows Cloud Files Mini Filter Driver. The flaw affects the Windows Cloud Files Mini Filter Driver component and could allow unauthorized disclosure of information from the vulnerable system. Specific technical details about the vulnerable code path, triggering conditions, and the exact nature of the exposed information are currently not available from the provided material.
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 contains a proof-of-concept (POC) exploit for CVE-2024-26160, an information disclosure vulnerability in the cldflt.sys driver on Windows 11 (22H2/23H2) prior to the March 2024 patch (KB5035853). The vulnerability arises from a lack of buffer size validation in the CldiPortProcessGetRangeInfo function, allowing a local attacker to leak kernel memory addresses by sending a specially crafted packet via the Cloud Files API. The main exploit logic is implemented in 'main.cpp', which sets up a sync root directory and placeholder file, constructs a malicious CLDFLT_HYDRATION_DATA packet, and sends it to the driver using FilterSendMessage. The exploit demonstrates the leak by dumping the output buffer. The code is written in C++ and is structured as a Visual Studio project. No network endpoints are involved; the attack vector is local, requiring the ability to interact with the Cloud Files API and the vulnerable driver.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.