dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-29996

HIGH · 7.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 10.0.10240.20651 / 10.0.14393.6981 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
Windows Common Log File System Driver Elevation of Privilege 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 confidence

This is an Elevation of Privilege vulnerability in the Windows Common Log File System (CLFS) driver. The vulnerability allows a local attacker to gain elevated privileges on the affected system. CVSS 7.8 indicates a local attack vector with low complexity, requiring some privileges but no user interaction.

MitigationApply the relevant Microsoft security updates for this vulnerability. Prioritize patching systems that are exposed or have higher privilege access requirements.

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
Windows 10 1507Operating system
Affected:< 10.0.10240.20651
Windows 10 1607Operating system
Affected:< 10.0.14393.6981
Windows 10 1809Operating system
Affected:< 10.0.17763.5820
Windows 10 21h2Operating system
Affected:< 10.0.19044.4412
Windows 10 22h2Operating system
Affected:< 10.0.19045.4412
Windows 11 21h2Operating system
Affected:< 10.0.22000.2960
Windows 11 22h2Operating system
Affected:< 10.0.22621.3593
Windows 11 23h2Operating system
Affected:< 10.0.22631.3593

CVSS 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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'. Alternatively, run 'ver' at command prompt to get the build number.
    Affected if The displayed build number is lower than the thresholds listed for your Windows release (1507: <20651, 1607: <6981, 1809: <5820, 21h2: <4412, 22h2: <4412, 11 21h2: <2960, 11 22h2: <3593, 11 23h2: <3593)
  2. Identify exact Windows release version
    Run 'winver' to confirm whether you are on Windows 10 1507, 1607, 1809, 21h2, 22h2 or Windows 11 21h2, 22h2, 23h2. The release name appears in the winver dialog window title or description.
    Affected if You are running any of the affected releases listed and your build number falls below the corresponding threshold
  3. Verify CLFS driver is present
    The vulnerability exists in the Windows Common Log File System (CLFS) driver. This driver is part of Windows and loads automatically. No specific configuration check needed - the driver (clfs.sys) loads with Windows.
    Affected if Your Windows version and build are within the affected ranges - the driver will be exploitable

You are affected if your Windows installation matches any of the version/release combinations listed AND your build number is below the specified threshold for that release.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.10240.20651 / 10.0.14393.6981 / 10.0.17763.5820 or later
Fixed in 10.0.10240.2065110.0.14393.698110.0.17763.5820
Interim mitigation

Apply the relevant Microsoft security updates for this vulnerability. Prioritize patching systems that are exposed or have higher privilege access requirements.

Recommended fix High confidence

Apply the April 2024 security update (KB5036892 or subsequent updates) which contains the fix for build versions: 10.0.10240.20651 (Win10 1507), 10.0.14393.6981 (Win10 1607), 10.0.17763.5820 (Win10 1809), 10.0.19044.4412 (Win10 21h2), 10.0.19045.4412 (Win10 22h2), 10.0.22000.2960 (Win11 21h2), 10.0.

  1. Open Settings on the Windows system
  2. Navigate to Windows Update (Update & Security > Windows Update)
  3. Click 'Check for updates' to download and install all available updates
  4. After installation, verify the OS build number matches or exceeds the fixed version for your Windows release
  5. Reboot the system if prompted to complete the installation
Caveat Standard Windows security update with no expected breaking changes; as an EoP vulnerability in the CLFS driver, there is low risk to normal system operation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29996 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-29996 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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