dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-30031

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 CNG Key Isolation Service 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 local Elevation of Privilege vulnerability in the Windows CNG (Cryptography Next Generation) Key Isolation Service. The vulnerability allows a local authenticated attacker to gain elevated privileges on the affected system by exploiting the insufficiently privileged key isolation service.

MitigationApply the Microsoft security update for CVE-2024-30031 via Windows Update or the Microsoft Update Catalog to patch the vulnerable CNG Key Isolation Service component.

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
High
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/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. Determine Windows build version
    Open Command Prompt or PowerShell and run: 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to see the full build number
    Affected if The build number is lower than the threshold for your Windows version (see version-specific thresholds in CVE details)
  2. Check exact OS build via PowerShell
    Run 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer' in PowerShell to identify the exact Windows release and build
    Affected if The version falls within any of the affected Windows 10 or 11 release ranges listed in the CVE
  3. Verify CNG Key Isolation Service version
    Locate the keyiso.dll file (typically in C:\Windows\System32\) and check its file version via Properties > Details, or run: 'Get-Item C:\Windows\System32\keyiso.dll | Select-Object VersionInfo'
    Affected if The file version is older than the patched version for your Windows release (versions vary by build)
  4. Confirm security update installation
    Check Windows Update history via Settings > Windows Update > Update history, or run: 'wmic qfe list' to list installed hotfixes
    Affected if The security update for CVE-2024-30031 (KB number varies by Windows version) is not listed as installed

You are affected if your Windows build number is below the threshold for your specific Windows version AND the CVE-2024-30031 security update is not 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.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-30031 via Windows Update or the Microsoft Update Catalog to patch the vulnerable CNG Key Isolation Service component.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.20651+ | Windows 10 1607: 10.0.14393.6981+ | Windows 10 1809: 10.0.17763.5820+ | Windows 10 21h2: 10.0.19044.4412+ | Windows 10 22h2: 10.0.19045.4412+ | Windows 11 21h2: 10.0.22000.2960+ | Windows 11 22h2: 10.0.22621.3593+ | Windows 11 23h2: 10.0.22631.3593+ (or install l

  1. Open Windows Update (Settings > Update & Security > Windows Update)
  2. Click 'Check for updates' to download and install the latest security updates
  3. Review the update history to confirm KB5034441 or subsequent security updates are installed
  4. Restart the system if prompted to complete the installation
  5. Verify the installed version meets the minimum threshold: Windows 10 1507 >= 10.0.10240.20651, Windows 10 1607 >= 10.0.14393.6981, Windows 10 1809 >= 10.0.17763.5820, Windows 10 21h2 >= 10.0.19044.4412, Windows 10 22h2 >= 10.0.19045.4412, Windows 11 21h2 >= 10.0.22000.2960, Windows 11 22h2 >= 10.0.22621.3593, Windows 11 23h2 >= 10.0.22631.3593
Caveat Standard Windows security updates typically have no breaking changes; however, test in a staging environment before broad deployment in enterprise environments

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
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,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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