dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-49090

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 an Elevation of Privilege vulnerability in the Windows Common Log File System (CLFS) driver. The vulnerability allows a local attacker to gain SYSTEM-level privileges by exploiting a flaw in the kernel-mode driver, potentially through improper handling of log file operations or memory references.

MitigationApply the relevant Microsoft Windows security update for CVE-2024-49090 through Windows Update or enterprise patch management systems as soon as testing permits.

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 version
    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 is lower than any of the thresholds listed in the affected versions (e.g., below 10.0.10240.20857 for Windows 10 1507, below 10.0.14393.7606 for Windows 10 1607, etc.)
  2. Check CLFS driver version
    Open Command Prompt as Administrator and run 'driverquery /v | findstr clfs' or check the file properties of C:\Windows\System32\clfs.sys to view the driver version
    Affected if The clfs.sys driver version is lower than the version corresponding to the fixed build for your Windows version, indicating the security update has not been applied
  3. Confirm vulnerability context
    Verify the system is running an affected Windows version by running 'winver' to confirm the exact build and version (such as 1507, 1607, 1809, 21h2, 22h2 for Windows 10, or 22h2, 23h2, 24h2 for Windows 11)
    Affected if The system is any Windows 10 or Windows 11 version listed in the affected products with a build number below the specified threshold and the CLFS driver has not been patched

You are affected if your Windows build number is lower than the threshold for your specific version AND the CLFS driver has not been updated to the patched version.

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 Microsoft Windows security update for CVE-2024-49090 through Windows Update or enterprise patch management systems as soon as testing permits.

Recommended fix High confidence

Upgrade to 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

  1. 1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which Windows 10 or 11 version is installed and check if it is below the fixed version for that release
  3. 3. Open Windows Update by going to Settings > Update & Security > Windows Update
  4. 4. Click 'Check for updates' to download and install the latest security updates
  5. 5. Alternatively, manually download and install the specific KB patch for this CVE from the Microsoft Update Catalog
  6. 6. Restart the system after updates are installed
  7. 7. Verify the installed version matches or exceeds the fixed build number for your Windows release
Caveat Standard Windows update risks apply - ensure critical workloads are backed up before applying updates

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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