dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2023-29324

MEDIUM · 6.5 CVSS v3.1 Published 2023-05-09
Fix available
A fix is available. Upgrade to 10.0.10240.19926 / 10.0.14393.5921 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click Patch available

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

A detailed technical summary for this CVE is being prepared.

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.19926
Windows 10 1607Operating system
Affected:< 10.0.14393.5921
Windows 10 1809Operating system
Affected:< 10.0.17763.4377
Windows 10 20h2Operating system
Affected:< 10.0.19042.2965
Windows 10 21h2Operating system
Affected:< 10.0.19044.2965
Windows 10 22h2Operating system
Affected:< 10.0.19045.2965
Windows 11 21h2Operating system
Affected:< 10.0.22000.1936
Windows 11 22h2Operating system
Affected:< 10.0.22000.1702

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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.19926 / 10.0.14393.5921 / 10.0.17763.4377 or later
Fixed in 10.0.10240.1992610.0.14393.592110.0.17763.4377
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Apply the corresponding security update: Windows 10 1507 to build 10.0.10240.19926 | Windows 10 1607 to build 10.0.14393.5921 | Windows 10 1809 to build 10.0.17763.4377 | Windows 10 20h2 to build 10.0.19042.2965 | Windows 10 21h2 to build 10.0.19044.2965 | Windows 10 22h2 to build 10.0.19045.2965 |

  1. Identify the current Windows version by running 'winver' or checking System Properties
  2. Determine which Windows 10 or 11 version is installed (1507, 1607, 1809, 20h2, 21h2, 22h2, or 11 21h2/22h2)
  3. Open Windows Settings > Update & Security > Windows Update
  4. Click 'Check for updates' to install the latest cumulative security update
  5. Alternatively, manually download the specific security update from the Microsoft Update Catalog: https://catalog.update.microsoft.com/
  6. Search for 'CVE-2023-29324' to find the applicable KB article for your Windows version
  7. Install the update and restart the system when prompted
  8. Verify the installation succeeded by checking that the OS build number meets or exceeds the fixed version for your release

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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