CVE-2024-38112
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 · uneditedWindows MSHTML Platform Spoofing 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 · low confidenceThis is a spoofing vulnerability in the Windows MSHTML platform, the rendering engine used by Internet Explorer and embedded web controls. The vulnerability allows attackers to misrepresent the origin or identity of content rendered by MSHTML, potentially tricking users into believing they're interacting with legitimate content or sites.
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< 10.0.10240.20710< 10.0.14393.7159< 10.0.17763.6054< 10.0.19044.4651< 10.0.19045.4651< 10.0.22000.3079< 10.0.22621.3880< 10.0.22631.3880CVSS 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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows version via systeminfoOpen Command Prompt and run `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` to retrieve the installed Windows version and build numberAffected if The displayed build number falls below any of the following thresholds: 10240.20710 (Win10 1507), 14393.7159 (Win10 1607), 17763.6054 (Win10 1809), 19044.4651 (Win10 21h2/22h2), 22000.3079 (Win11 21h2), 22621.3880 (Win11 22h2), or 22631.3880 (Win11 23h2)
-
Check Windows version via winverRun `winver` from the Run dialog or command line to display the Windows version and build number in a graphical windowAffected if The build number shown is lower than the thresholds listed in the affected versions for your specific Windows release (10 or 11)
-
Check Windows version via registryOpen Registry Editor and navigate to `HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion`, then note the values of `CurrentBuild` and `DisplayVersion`Affected if The `CurrentBuild` number is less than the affected build threshold for your Windows version
-
Verify MSHTML engine component presenceCheck for the presence of mshtml.dll by running `dir %SystemRoot%\System32\mshtml.dll` in Command PromptAffected if The file exists (which it does on all affected systems) and the Windows version is below the patched thresholds, indicating the unpatched MSHTML platform is in use
A system is affected if it is running any Windows 10 or Windows 11 version with a build number lower than the thresholds listed in the affected versions, since those versions contain the vulnerable MSHTML platform.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.10240.2071010.0.14393.715910.0.17763.6054
Apply Microsoft security updates for CVE-2024-38112 when released. Until then, restrict or disable MSHTML components where possible and exercise caution with untrusted web content.
Install the latest Windows security updates (KB5034441 or later cumulative update) - specific builds: Windows 10 1507 to 10.0.10240.20710, Windows 10 1607 to 10.0.14393.7159, Windows 10 1809 to 10.0.17763.6054, Windows 10 21h2 to 10.0.19044.4651, Windows 10 22h2 to 10.0.19045.4651, Windows 11 21h2 t
- Open Settings on the Windows system
- Navigate to Windows Update (Update & Security > Windows Update)
- Click 'Check for updates' to download and install the latest security updates
- Verify the installed KB update includes the CVE-2024-38112 fix by checking the update history
- Confirm the Windows build number matches or exceeds the fixed version for your Windows release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-38112 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-38112 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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