dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2023-35385

CRITICAL · 9.8 CVSS v3.1 Published 2023-08-08
Fix available
A fix is available. Upgrade to 10.0.10240.20107 / 10.0.14393.6167 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Microsoft Message Queuing (MSMQ) Remote Code Execution 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
How this class of weakness works · CWE-190

An arithmetic operation produces a value too large for its type and wraps around to an unexpected — often tiny or negative — number. That miscalculated value then drives a memory allocation or a bounds check, opening the door to corruption. The fix is checked arithmetic and validating sizes before they're used.

General guidance for the integer overflow class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.20107
Windows 10 1607Operating system
Affected:< 10.0.14393.6167
Windows 10 1809Operating system
Affected:< 10.0.17763.4737
Windows 10 21h2Operating system
Affected:< 10.0.19044.3324
Windows 10 22h2Operating system
Affected:< 10.0.19045.3324
Windows 11 21h2Operating system
Affected:< 10.0.22000.2295
Windows 11 22h2Operating system
Affected:< 10.0.22621.2134
Windows Server 2008Operating system
Affected:all versions= r2

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

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

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.20107 / 10.0.14393.6167 / 10.0.17763.4737 or later
Fixed in 10.0.10240.2010710.0.14393.616710.0.17763.4737
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Windows 10 1507: 10.0.10240.20107+ | Windows 10 1607: 10.0.14393.6167+ | Windows 10 1809: 10.0.17763.4737+ | Windows 10 21h2: 10.0.19044.3324+ | Windows 10 22h2: 10.0.19045.3324+ | Windows 11 21h2: 10.0.22000.2295+ | Windows 11 22h2: 10.0.22621.2134+

  1. Navigate to https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-35385 to obtain the specific security update for your Windows version
  2. Open Windows Update by going to Settings > Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the applicable security patch
  4. Alternatively, download the specific security update from the Microsoft Update Catalog using the KB number provided in the MSRC guide
  5. For Windows Server 2008 (end-of-life with no patch), disable the MSMQ service: Open Services, find 'Message Queuing', right-click and select 'Stop', then set Startup type to 'Disabled'
  6. Restart the system after applying the update to ensure the vulnerability is remediated
Caveat Windows Server 2008 has no patch; requires service disablement or migration to supported OS

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 $3,550. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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