CVE-2024-30034
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWindows Cloud Files Mini Filter Driver Information Disclosure Vulnerability
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceVulnerability in Windows Cloud Files Mini Filter Driver allows information disclosure. The specific nature of the exposed information and exact exploitation mechanism are not detailed in available documentation. The CVSS 5.5 indicates a medium-severity flaw requiring low complexity exploitation with no authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.0.17763.5820< 10.0.19044.4412< 10.0.19045.4412< 10.0.22000.2960< 10.0.22621.3593< 10.0.22631.3593< 10.0.17763.5820< 10.0.20348.2461CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Windows versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the exact Windows build numberAffected if The Windows build number is lower than any of these thresholds: 10.0.17763.5820 (Windows 10 1809/Server 2019), 10.0.19044.4412 (Windows 10 21h2), 10.0.19045.4412 (Windows 10 22h2), 10.0.22000.2960 (Windows 11 21h2), 10.0.22621.3593 (Windows 11 22h2), 10.0.22631.3593 (Windows 11 23h2), or 10.0.20348.
-
Verify Cloud Files Mini Filter Driver is presentRun 'fltmc.exe filters' or check the driver file exists at %SystemRoot%\System32\drivers\cldflt.sysAffected if The Cloud Files Mini Filter Driver (cldflt) is loaded or the driver file exists on the system
-
Retrieve driver versionRight-click cldflt.sys in %SystemRoot%\System32\drivers\, select Properties, then view the Details tab for the File Version, or run 'powershell (Get-Item "C:\Windows\System32\drivers\cldflt.sys").VersionInfo.FileVersion'Affected if The driver version number is lower than the corresponding threshold for your Windows version (for example, below 10.0.17763.5820 on Windows 10 1809 or Windows Server 2019)
You are affected if your Windows build falls within the listed version ranges AND the Cloud Files Mini Filter Driver is present with a version lower than the specified threshold.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.0.17763.582010.0.19044.441210.0.19045.4412
Apply Microsoft security updates for CVE-2024-30034 through Windows Update or enterprise patch management systems. Verify the Cloud Files Mini Filter Driver version post-patch.
Windows 10 1809: build 10.0.17763.5820 | Windows 10 21h2: build 10.0.19044.4412 | Windows 10 22h2: build 10.0.19045.4412 | Windows 11 21h2: build 10.0.22000.2960 | Windows 11 22h2: build 10.0.22621.3593 | Windows 11 23h2: build 10.0.22631.3593 | Windows Server 2019: build 10.0.17763.5820 | Windows S
- Identify the current Windows version and build number by running 'winver' or 'systeminfo'
- Open Windows Update by navigating to Settings > Update & Security > Windows Update
- Click 'Check for updates' to receive the latest Microsoft security patch for CVE-2024-30034
- Alternatively, navigate to Microsoft Update Catalog (https://www.catalog.update.microsoft.com) and search for CVE-2024-30034 or the specific KB article associated with this vulnerability
- Download and install the appropriate security update for your Windows version
- Restart the system when prompted to complete the installation
- Verify the update was installed successfully by checking the installed updates in Control Panel > Programs and Features > View installed updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30034 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-30034 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data