CVE-2024-30085: CVE-2024-30085: Windows Cloud Files Mini Filter Driver Elevation of Privilege Vulnerability

What it is

Windows Cloud Files Mini Filter Driver Elevation of Privilege Vulnerability

Exploitation evidence

First exploit evidence seen: 2024-12-19 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

Metasploit

• exploit/windows/local/cve_2024_30085_cloud_files: Windows Cloud File Mini Filer Driver Heap Overflow (disclosure 2024-12-19)

GitHub proof-of-concept repositories below quality bar

2 public repositories from 2 accounts, first seen 2024-12-25.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: Rapid7 Metasploit Framework module metadata · nomi-sec/PoC-in-GitHub.

How to fix it

Fixed versions

• microsoft windows 10 1809: upgrade to 10.0.17763.5936 or later
• microsoft windows 10 21h2: upgrade to 10.0.19044.4529 or later
• microsoft windows 10 22h2: upgrade to 10.0.19045.4529 or later
• microsoft windows 11 21h2: upgrade to 10.0.22000.3019 or later
• microsoft windows 11 22h2: upgrade to 10.0.22621.3737 or later
• microsoft windows 11 23h2: upgrade to 10.0.22631.3737 or later
• microsoft windows server 2019: upgrade to 10.0.17763.5936 or later
• microsoft windows server 2022: upgrade to 10.0.20348.2522 or later
• microsoft windows server 2022 23h2: upgrade to 10.0.25398.950 or later

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

• https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-30085 (Patch, Vendor Advisory)

MITRE ATT&CK mitigations for this chain

• M1050 Exploit Protection (for T1203, T1068) : Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. Control flow integrity checking is another way to potentially identify and stop a software exploi
• M1051 Update Software (for T1203, T1068) : Perform regular software updates to mitigate exploitation risk. Keeping software up-to-date with the latest security patches helps prevent adversaries from exploiting known vulnerabilities in client software, reducing the risk of successful attacks.
• M1048 Application Isolation and Sandboxing (for T1203, T1068) : Browser sandboxes can be used to mitigate some of the impact of exploitation, but sandbox escapes may still exist. Other types of virtualization and application microsegmentation may also mitigate the impact of client-side exploitation. Risks of additional exploits and weaknesses in those systems may still exist.
• M1019 Threat Intelligence Program (for T1068) : Develop a robust cyber threat intelligence capability to determine what types and levels of threat may use software exploits and 0-days against a particular organization.
• M1038 Execution Prevention (for T1068) : Consider blocking the execution of known vulnerable drivers that adversaries may exploit to execute code in kernel mode. Validate driver block rules in audit mode to ensure stability prior to production deployment.

Detection Generic guidance

• Execution: Watch for the service process spawning shells or script interpreters (cmd.exe, powershell, sh, bash, python) via EDR process-tree rules.
• Privilege Escalation: Alert on processes gaining SYSTEM/root unexpectedly, and on exploitation crashes of privileged services.

Response checklist Generic guidance

1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.