dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-30027

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
NTFS 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

A Windows NTFS elevation of privilege vulnerability (CVSS 7.8) that allows a low-privileged attacker to gain higher system privileges through a flaw in NTFS file system handling on affected Windows systems.

MitigationApply the Microsoft security update for CVE-2024-30027 via Windows Update or patch management systems to address the NTFS privilege escalation 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.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"' to display the installed Windows version and build number
    Affected if The build number is less than the fixed version for your Windows release (1507: < 10240.20651, 1607: < 14393.6981, 1809: < 17763.5820, 21h2: < 19044.4412, 22h2: < 19045.4412, 11 21h2: < 22000.2960, 11 22h2: < 22621.3593, 11 23h2: < 22631.3593)
  2. Confirm NTFS file system is in use
    Open Command Prompt and run 'fsutil fsinfo volumeinfo C:' (or any local drive letter) to verify the file system type is NTFS
    Affected if The file system is NTFS (this is the default for Windows system drives and most data drives)
  3. Verify current user context
    Run 'whoami /groups' in Command Prompt to see the current user's privilege level
    Affected if The user is a local user with limited privileges (not an administrator) and the system is unpatched

The environment is affected if the installed Windows build number falls below the fixed version thresholds AND the system uses NTFS file system AND the attacker has local access to execute the exploit.

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 Microsoft security update for CVE-2024-30027 via Windows Update or patch management systems to address the NTFS privilege escalation vulnerability.

Recommended fix High confidence

Upgrade to the May 2024 Windows Security Update (KB5037771 or later) which includes the fix for CVE-2024-30027; specific fixed builds include: Windows 10 1507 build 10240.20651, Windows 10 1607 build 14393.6981, Windows 10 1809 build 17763.5820, Windows 10 21h2 build 19044.4412, Windows 10 22h2 buil

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo'
  2. Determine which version bracket your system falls into (Windows 10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 21h2, 22h2, 23h2)
  3. Apply the relevant Microsoft security update from May 2024 (KB5037771 or later) that addresses CVE-2024-30027
  4. After patching, verify the installed build matches or exceeds the fixed version for your release (e.g., Windows 10 22h2 should be >= 10.0.19045.4412)
  5. Restart the system as required by the security update
Caveat Standard Windows security update - no expected breaking changes; as with any system update, ensure backups exist and test critical applications after reboot

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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