dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-49088

HIGH · 7.8 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 10.0.10240.20857 / 10.0.14393.7606 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 a privilege escalation vulnerability in the Windows Common Log File System (CLFS) driver. The vulnerability allows an authenticated attacker to elevate their privileges to SYSTEM level by exploiting improper validation or handling within the CLFS driver component.

MitigationApply the relevant Windows security update (KB5044284 or subsequent patches) to all affected Windows systems to remediate this vulnerability.

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.20857
Windows 10 1607Operating system
Affected:< 10.0.14393.7606
Windows 10 1809Operating system
Affected:< 10.0.17763.6659
Windows 10 21h2Operating system
Affected:< 10.0.19044.5247
Windows 10 22h2Operating system
Affected:< 10.0.19045.5247
Windows 11 22h2Operating system
Affected:< 10.0.22621.4602
Windows 11 23h2Operating system
Affected:< 10.0.22631.4602
Windows 11 24h2Operating system
Affected:< 10.0.26100.2605

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 build number
    Open Command Prompt or PowerShell and run `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` to display the installed Windows version and build number.
    Affected if The build number displayed is lower than any of the fixed versions for your Windows release (10.0.10240.20857 for 1507, 10.0.14393.7606 for 1607, 10.0.17763.6659 for 1809, 10.0.19044.5247 for 21h2, 10.0.19045.5247 for 22h2, 10.0.22621.4602 for 11 22h2, 10.0.22631.4602 for 11 23h2, 10.0.26100.2605 fo
  2. Identify Windows release version
    Run `winver` and note the release name (such as 1507, 1607, 1809, 21h2, 22h2) or for Windows 11 check Settings > System > About to identify 22h2, 23h2, or 24h2.
    Affected if The identified release matches any of the affected versions listed and the build number from step 1 is below the corresponding threshold.
  3. Confirm CLFS driver presence
    Open PowerShell and run `Get-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Services\CLFS' -ErrorAction SilentlyContinue` to check if the Common Log File System driver is registered on the system.
    Affected if The CLFS driver registry key exists, indicating the driver is present and could be exploitable if the version is vulnerable.
  4. Verify authenticated user context
    This vulnerability requires an authenticated user account. Check the current user context by running `whoami` in Command Prompt or PowerShell.
    Affected if Any non-privileged authenticated user account exists on the system, which could potentially exploit this vulnerability if the Windows version is affected.

If the system runs any Windows 10 or 11 version with a build number lower than the fixed thresholds listed for its respective release, the CLFS driver is present, and an authenticated user exists, the environment is affected by CVE-2024-49088.

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.20857 / 10.0.14393.7606 / 10.0.17763.6659 or later
Fixed in 10.0.10240.2085710.0.14393.760610.0.17763.6659
Interim mitigation

Apply the relevant Windows security update (KB5044284 or subsequent patches) to all affected Windows systems to remediate this vulnerability.

Recommended fix High confidence

Windows 10 1507: build 10.0.10240.20857 | Windows 10 1607: build 10.0.14393.7606 | Windows 10 1809: build 10.0.17763.6659 | Windows 10 21h2: build 10.0.19044.5247 | Windows 10 22h2: build 10.0.19045.5247 | Windows 11 22h2: build 10.0.22621.4602 | Windows 11 23h2: build 10.0.22631.4602 | Windows 11 2

  1. Identify the current Windows version and build by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Determine which version branch applies (e.g., Windows 10 22h2, Windows 11 23h2, etc.)
  3. Open Windows Update by pressing Win+I and navigating to Windows Update, or manually download the security update from the Microsoft Update Catalog (search for CVE-2024-49088)
  4. Install the applicable security update for your Windows version
  5. Restart the system when prompted to complete the installation
  6. Verify the build number matches or exceeds the fixed version for your branch using 'winver'
Caveat Standard Windows security update; no breaking changes expected for most users

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-49088 — 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-49088 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