dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2023-35339

HIGH · 7.5 CVSS v3.1 Published 2023-07-11
Fix available
A fix is available. Upgrade to 10.0.10240.20048 / 10.0.14393.6085 or later.
See remediation →
84/100
Remediation priority · High
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 CryptoAPI Denial of Service 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-400

A single request can consume unbounded CPU, memory, or connections, so a modest amount of malicious traffic exhausts the service. The result is denial of service for everyone else. Remediation is enforcing limits, quotas, and timeouts on what any one request can use.

General guidance for the uncontrolled resource consumption 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.20048
Windows 10 1607Operating system
Affected:< 10.0.14393.6085
Windows 10 1809Operating system
Affected:< 10.0.17763.4645
Windows 10 21h2Operating system
Affected:< 10.0.19041.3208
Windows 10 22h2Operating system
Affected:< 10.0.19045.3208
Windows 11 21h2Operating system
Affected:< 10.0.22000.2176
Windows 11 22h2Operating system
Affected:< 10.0.22621.1992
Windows Server 2016Operating system
Affected:all versions

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.20048 / 10.0.14393.6085 / 10.0.17763.4645 or later
Fixed in 10.0.10240.2004810.0.14393.608510.0.17763.4645
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

Windows 10 1507: 10.0.10240.20048 | Windows 10 1607: 10.0.14393.6085 | Windows 10 1809: 10.0.17763.4645 | Windows 10 21h2: 10.0.19041.3208 | Windows 10 22h2: 10.0.19045.3208 | Windows 11 21h2: 10.0.22000.2176 | Windows 11 22h2: 10.0.22621.1992 | Windows Server 2016: apply all available cumulative up

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Note the Windows build number (e.g., 10.0.19045.xxxx)
  3. Determine the minimum fixed build for your Windows version from the vulnerability advisory
  4. Open Windows Settings > Update & Security > Windows Update
  5. Click 'Check for updates' to download and install the latest cumulative update
  6. Verify the installed build number matches or exceeds the minimum fixed build for your Windows version
  7. Restart the system if prompted to complete the update installation
  8. Alternatively, use Windows Server Update Services (WSUS) or Microsoft Update Catalog to deploy the update to enterprise environments
Caveat Standard Windows cumulative update considerations apply; test updates in non-production environments before broad deployment

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,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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