CVE-2024-30040
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 Security Feature Bypass 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 confidenceThis is a security feature bypass vulnerability in the Windows MSHTML platform, which is the rendering engine used by Internet Explorer and embedded in Office applications. The vulnerability allows an attacker to circumvent security mechanisms, potentially enabling remote code execution or other attacks through specially crafted web content or documents.
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.20651< 10.0.14393.6981< 10.0.17763.5820< 10.0.19044.4412< 10.0.19045.4412< 10.0.22000.2960< 10.0.22621.3593< 10.0.22631.3593CVSS 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 against affected rangesRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' and compare the build number to the affected version thresholds (10.0.10240.20651, 10.0.14393.6981, 10.0.17763.5820, 10.0.19044.4412, 10.0.19045.4412, 10.0.22000.2960, 10.0.22621.3593, 10.0.22631.3593)Affected if The installed build number is lower than the corresponding threshold for your Windows version
-
Verify MSHTML Platform is not disabledCheck registry key HKLM\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings for 'MSHTMLEnabled' DWORD value, or look for Group Policy settings under Computer Configuration/Administrative Templates/Windows Components/Internet Explorer that disable MSHTMLAffected if MSHTML is not explicitly disabled through policy or registry setting (value is absent or not set to 1)
-
Confirm ActiveX control execution is not restrictedCheck Internet Explorer security zone settings via registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\Zones or via Group Policy under Computer Configuration/Administrative Templates/Windows Components/Internet Explorer/Security Features/ActiveX, and verify if 'Allow ActiveX' is permitted for relevant zonesAffected if ActiveX controls are allowed in any zone (especially Intranet or Internet zone) rather than blocked for all sites
A system is likely affected if it runs a Windows version below the fixed build numbers AND has MSHTML rendering enabled with ActiveX controls permitted.
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.2065110.0.14393.698110.0.17763.5820
Apply Microsoft security updates for CVE-2024-30040 via Windows Update or manual patch deployment. Ensure Windows systems and Microsoft Office installations are patched promptly.
Windows 10 1507 to >=10.0.10240.20651 | Windows 10 1607 to >=10.0.14393.6981 | Windows 10 1809 to >=10.0.17763.5820 | Windows 10 21h2 to >=10.0.19044.4412 | Windows 10 22h2 to >=10.0.19045.4412 | Windows 11 21h2 to >=10.0.22000.2960 | Windows 11 22h2 to >=10.0.22621.3593 | Windows 11 23h2 to >=10.0.
- Identify the current Windows version by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
- Determine which Windows release (1507, 1607, 1809, 21h2, 22h2, 11 21h2, 11 22h2, or 11 23h2) matches your current version
- Open Windows Update settings (Settings > Update & Security > Windows Update)
- Check for and install the latest cumulative security update for your Windows version
- Alternatively, manually download and install the security update from the Microsoft Update Catalog matching your Windows version (search for CVE-2024-30040)
- After installation, restart the system to apply the update
- Verify the update was applied by checking the installed updates list or running 'winver' to confirm the version matches or exceeds the fixed version for your release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30040 — 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-30040 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