dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2024-21417

HIGH · 8.8 CVSS v3.1 Published 2024-07-10
Fix available
A fix is available. Upgrade to 10.0.17763.6054 / 10.0.19044.4651 or later.
See remediation →
90/100
Remediation priority · Urgent
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 Text Services Framework 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 Windows Elevation of Privilege vulnerability in the Text Services Framework component. The vulnerability allows an attacker to gain higher system privileges, potentially moving from a low-privileged user context to administrator or SYSTEM level access.

MitigationApply the Microsoft security update for CVE-2024-21417 via Windows Update or deploy the corresponding patch from Microsoft's monthly security release to affected Windows systems.

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 1809Operating system
Affected:< 10.0.17763.6054
Windows 10 21h2Operating system
Affected:< 10.0.19044.4651
Windows 10 22h2Operating system
Affected:< 10.0.19045.4651
Windows 11 21h2Operating system
Affected:< 10.0.22000.3079
Windows 11 22h2Operating system
Affected:< 10.0.22621.3880
Windows 11 23h2Operating system
Affected:< 10.0.22631.3880
Windows Server 2019Operating system
Affected:< 10.0.17763.6054
Windows Server 2022Operating system
Affected:< 10.0.20348.2582

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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. Check Windows build version
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to display the full build number
    Affected if The displayed build number falls below the threshold for your Windows release (17763.6054, 19044.4651, 19045.4651, 22000.3079, 22621.3880, 22631.3880, or 20348.2582)
  2. Identify exact Windows release
    Run 'ver' at command prompt or check System Properties to determine if you are on Windows 10 1809, 10 21h2, 10 22h2, Windows 11 21h2, 22h2, 23h2, or Windows Server 2019/2022
    Affected if Your specific Windows release and build number is lower than the corresponding threshold listed in the affected versions
  3. Verify Text Services Framework component
    Check that the Text Services Framework (msctf.dll) exists in the system. Run 'dir %SystemRoot%\System32\msctf.dll' to confirm the file is present
    Affected if The file exists (this is required for the vulnerability to apply; all unpatched systems with this component are affected)
  4. Confirm patch installation status
    Open Settings > Windows Update > View update history, or run 'wmic qfe list' to list installed hotfixes. Look for the February 2024 security update (KB5002537 or later monthly rollup)
    Affected if The February 2024 security update or later monthly update is NOT installed, indicating the system is unpatched

Your system is affected if it runs any of the listed Windows versions with a build number lower than the corresponding threshold and the February 2024 security update has not been applied.

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.17763.6054 / 10.0.19044.4651 / 10.0.19045.4651 or later
Fixed in 10.0.17763.605410.0.19044.465110.0.19045.4651
Interim mitigation

Apply the Microsoft security update for CVE-2024-21417 via Windows Update or deploy the corresponding patch from Microsoft's monthly security release to affected Windows systems.

Recommended fix High confidence

Windows 10 1809/Server 2019: build 17763.6054+ | Windows 10 21H2: build 19044.4651+ | Windows 10 22H2: build 19045.4651+ | Windows 11 21H2: build 22000.3079+ | Windows 11 22H2: build 22621.3880+ | Windows 11 23H2: build 22631.3880+ | Windows Server 2022: build 20348.2582+

  1. Open Settings > Update & Security > Windows Update
  2. Click 'Check for updates' to receive the latest security patches
  3. Ensure the update includes the build version >= 10.0.17763.6054 for Windows 10 1809/Server 2019, >= 10.0.19044.4651 for Windows 10 21H2, >= 10.0.19045.4651 for Windows 10 22H2, >= 10.0.22000.3079 for Windows 11 21H2, >= 10.0.22621.3880 for Windows 11 22H2, >= 10.0.22631.3880 for Windows 11 23H2, or >= 10.0.20348.2582 for Windows Server 2022
  4. Alternatively, manually download and install the security update from the Microsoft Update Catalog for your specific Windows version
  5. Restart the system after installing the update
  6. Verify the installed version matches or exceeds the required build number via winver or systeminfo

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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