dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 27 Apr 2026.
Windows 10 1507Operating system · Microsoft

CVE-2023-36424

HIGH · 7.8 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 10.0.10240.20308 / 10.0.14393.6452 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click Patch available

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 that allows a local authenticated attacker to gain SYSTEM-level privileges. The CVSS 7.8 score indicates low attack complexity, no privileges required, and no user interaction needed for exploitation.

MitigationApply the Microsoft security update for CVE-2023-36424 through Windows Update or deploy the corresponding patch via organizational patch management processes.

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.20308
Windows 10 1607Operating system
Affected:< 10.0.14393.6452
Windows 10 1809Operating system
Affected:< 10.0.17763.5122
Windows 10 21h2Operating system
Affected:< 10.0.19044.3693
Windows 10 22h2Operating system
Affected:< 10.0.19045.3693
Windows 11 21h2Operating system
Affected:< 10.0.22000.2600
Windows 11 22h2Operating system
Affected:< 10.0.22621.2715
Windows 11 23h2Operating system
Affected:< 10.0.22631.2715

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
    Run 'winver' or execute 'Get-ComputerInfo | Select-Object WindowsVersion, OsBuildNumber' in PowerShell to retrieve the exact Windows version and build number
    Affected if The build number falls below the threshold for your Windows release: 10240.20308 for 1507, 14393.6452 for 1607, 17763.5122 for 1809, 19044.3693 for 21h2, 19045.3693 for 22h2, 22000.2600 for Win11 21h2, 22621.2715 for Win11 22h2, or 22631.2715 for Win11 23h2
  2. Confirm Windows edition
    Run 'systeminfo' or check the system properties to verify which Windows 10 or 11 release (1507, 1607, 1809, 21h2, 22h2, or Windows 11 variants) is installed
    Affected if The installed edition matches one of the affected versions listed and the build number is below the corresponding threshold
  3. Verify CLFS driver is present
    Check that the Common Log File System driver exists at the expected system location. The driver file is typically located in the System32 directory and is a core Windows kernel component present on all affected versions
    Affected if The system is running an affected Windows version as determined by the build number check, meaning the CLFS driver in that version is vulnerable

You are affected if your Windows version build number is lower than the threshold listed for your specific Windows release (10 1507 through 11 23h2), because that indicates the unpatched CLFS driver is installed.

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.20308 / 10.0.14393.6452 / 10.0.17763.5122 or later
Fixed in 10.0.10240.2030810.0.14393.645210.0.17763.5122
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the Microsoft security update for CVE-2023-36424 through Windows Update or deploy the corresponding patch via organizational patch management processes.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.20308+ | Windows 10 1607: 10.0.14393.6452+ | Windows 10 1809: 10.0.17763.5122+ | Windows 10 21h2: 10.0.19044.3693+ | Windows 10 22h2: 10.0.19045.3693+ | Windows 11 21h2: 10.0.22000.2600+ | Windows 11 22h2: 10.0.22621.2715+ | Windows 11 23h2: 10.0.22631.2715+

  1. Identify the Windows version and build currently installed using 'winver' or 'systeminfo'
  2. Determine the applicable security update for CVE-2023-36424 from the Microsoft Security Response Center (msrc.microsoft.com)
  3. Apply the relevant Windows security update via Windows Update, WSUS, or by downloading the update from the Microsoft Update Catalog
  4. Restart the system as prompted to complete the update installation
  5. Verify the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows security update; no expected breaking changes for typical deployments

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

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get it fixed fast

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-2023-36424 — 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-2023-36424 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